Remove the remote HTTP connection to fetch the filesize #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The performance of this plugin on my local Altis site was at a crawl. Each request to the attachments query Ajax endpoint was taking 20-30 seconds.
I narrowed down the problem to this call to
get_headers()
. It's called for each file in the result and performs a server side HTTP request to the URL in order to fetch its size. I can see that the file size is not exposed in the WordPress REST API, which I guess is the reason this code exists.Removing this call brings the performance back to acceptable levels.
Removing this means the
File size:
section in the media manager contains no value, but this is a fair tradeoff to bring the performance back.Regarding exposing the file size, we could:
In the meantime I propose simply removing this.