[wp-trac] [WordPress Trac] #40441: High server resource usage and timeouts during image uploads

[WordPress Trac]

#40441: High server resource usage and timeouts during image uploads
-------------------------+------------------------------
 Reporter:  enshrined    |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Media        |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+------------------------------

Comment (by blobfolio):

 @enshrined, I apologize, I thought the concept of some sort of recoverable
 /queue-based thumbnail generation was already a foregone conclusion. That
 is by far the best overall solution. I thought this thread was more about
 identifying where specifically (aside from "doing too many things in one
 go") the image processes are too heavy for the types of servers people are
 actually using.

 Outside of the chain of image processing itself, the single biggest issue
 I see is not WordPress, but what users are doing to it and where they're
 trying to do it from. To that end, I see the decision (from the WP side)
 as moot. We can either offer patches that could help extend the
 portability of the software to less capable environments (that people are
 already using anyway), or not. That would be an "option", definitely, and
 one that I wouldn't want to even see as a default. But having it in place
 would provide a solution for people in that situation.

 You're right, the `->multi_resize()` function does preserve the source for
 the duration of its operation. But after that it is gone. Since so much
 image handling is achieved by passing filenames and attachment IDs through
 filters, most hookable alterations would have no choice but to
 reinstantiate the editor object anew. Static cache would preserve the
 resource between instances (though to keep memory from blowing up we
 probably would want to keep it to just the "last" file). All in all this
 would probably be a bigger deal on Windows than Linux since file system
 operations are more expensive to perform there (under Windows, that is).

--
Ticket URL: <https://core.trac.wordpress.org/ticket/40441#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform