[wp-trac] [WordPress Trac] #55443: Create WebP sub-sizes and use for output
WordPress Trac
noreply at wordpress.org
Thu Aug 18 19:01:14 UTC 2022
#55443: Create WebP sub-sizes and use for output
-------------------------------------------------+-------------------------
Reporter: adamsilverstein | Owner:
| adamsilverstein
Type: enhancement | Status: assigned
Priority: normal | Milestone: 6.1
Component: Media | Version: 6.0
Severity: normal | Resolution:
Keywords: has-unit-tests needs-dev-note | Focuses:
needs-docs needs-user-docs needs-patch 2nd- | performance
opinion needs-testing |
-------------------------------------------------+-------------------------
Comment (by adamsilverstein):
> Is there any data about how much more resources (memory, processing
time, etc.) are needed when uploading different image sizes? Any estimate
about how many sites may be affected by that? Any suggestions on how to
deal with it? Do you know what happens when post-processing of an uploaded
image fails?
In general WebPs are a little more resource intensive to generate vs.
JPEGs. Only sites that have WebP support will be affected though, and
while we expect support is widespread since it has been available for so
long, but we don't have hard data (we will start gathering data since
#48116).
The additional resources at upload time need to be weighed against the
reduced resources of serving the smaller WebP image, especially since
serving typically occurs several orders of magnitude more frequently than
uploading.
If uploading fails after all the retries, the user has the same experience
as currently: they are left with a broken, unusable image. That can
probably be fixed, although I don't think this change will increases
failure rates.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/55443#comment:119>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list