A few Eleventy build server image optimization tests for the project I’m currently working on (×1088 images):
formats: webp, auto =>
❄️ cold cache: 4m 33s
🔥 warm cache: 36s
formats: avif, webp, auto =>
❄️ cold cache: 11m 32s
🔥 warm cache: 38s
Do y’all think the AVIF build cost is worth it if the build server cache is ~always warm?
=> More informations about this toot | More toots from zachleat@zachleat.com
@zachleat 2 seconds for a more compatible, higher efficiency codec? yeah i’d say so. that time difference may even be just noise depending on what else the build server is doing
=> More informations about this toot | More toots from exchgr@mastodon.world
@exchgr yeah 100% I think the uneasiness there is mostly around the the reliability of the build cache — largely out of my control
=> More informations about this toot | More toots from zachleat@zachleat.com
@zachleat oo yeah that might be concerning then. not sure if this helps or what the use case is, but i’ve been using cloudflare images, which handles the transcoding for me (although it’s limited in some slightly frustrating ways)
=> More informations about this toot | More toots from exchgr@mastodon.world This content has been proxied by September (3851b).Proxy Information
text/gemini