• Resolved Dr. Melvin Temo

    (@temovision)


    IMAGE comparism: It is difficult to do a test run side by side to compare the savings against real picture links. The statistics show the savings but it will be also good to see the avif and jpg example pic or link side by side to see if the quality is degraded or not.

    In that way, if there is an initial test run of pics say 10 or 20, one can objectly do that and determine which compression quaity he or she is going to settle for.

    BATCH number per cron: I noticed it is limited to 20 max. That is so conservative. 50, 100, 200, or maybe custom while warning the user about higher limits maybe a good idea to incorporate.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Marco Di Giacomantonio

    (@marcodigiacomantonio)

    Both of these are good product suggestions — thanks for thinking it through.

    On the side-by-side image comparison: there isn’t one today, and I agree it’d be genuinely useful — a sample test run that shows the original and the AVIF next to each other with their file sizes, so you can judge quality vs. savings before committing to a quality setting. It’s a proper feature rather than a quick tweak, so I’m putting it on the roadmap for a dedicated release rather than rushing it.

    On the batch number: you’re right that the setting is capped at 20, but it’s worth knowing that number is more of a soft ceiling than a hard throughput limit. The plugin already sizes each batch adaptively — it estimates per-image memory cost against your server’s available RAM and processing time, takes the safest of those, and automatically scales the batch down mid-run if it gets close to a timeout or memory pressure. So in practice the engine self-tunes regardless of whether you set 3 or 20.

    That said, I’ll raise the configurable ceiling to 50 (which matches the internal safety limit) in an upcoming release, with a note in the UI explaining the auto-throttling. I’d hold off going higher than that — beyond 50 would mean removing the memory/timeout safeguards, which is where things start crashing on shared hosting. 50 with adaptive sizing underneath is the sweet spot between throughput and not blowing up a site.

    Appreciate the detailed feedback.

    Marco
    I-PR AVIF Converter

    Thread Starter Dr. Melvin Temo

    (@temovision)

    Great. I will love to have a notification when it is updated and now hits the 50 limit. 50 is very fair while maybe cautioning the user after potential failure or so.

    Thank you for your kind words. I hope my suggestions help make the plug in better.

    Thread Starter Dr. Melvin Temo

    (@temovision)

    and that’s fine, regarding the test run. I agree, that’s a proper feature. It is ok to take time to implement it

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.