Support » Plugin: EWWW Image Optimizer » Scan did not complete, will try again

  • Resolved PrajwalDesai

    (@prajwaldesai)


    I am not sure why I am getting this error. When i go to Media > Bulk Optimize and click scan for unoptimized images, i get a red line scan did not complete, will try again. I may have around 4k images. I have updated the plugin to latest Version 3.2.5. Please fix this in next update.

    Thanks,
    PD

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author nosilver4u

    (@nosilver4u)

    The plugin is supposed to display that message if the scan gets interrupted for any reason. Please let it run until it either completes or fails entirely, and let me know what happens. If it fails entirely, and you would like to troubleshoot further, please contact me here: https://ewww.io/contact-us/

    Thread Starter PrajwalDesai

    (@prajwaldesai)

    i see this message after long time – Operation timed out, you may need to increase the max_execution_time for PHP

    I checked my phpinfo, my max_execution_time is set to 900

    Plugin Author nosilver4u

    (@nosilver4u)

    Thanks for confirming, should have an update out later today that addresses the issue. It is supposed to stop the scan after 15 seconds, return how many images have been scanned, and then start another batch. This would prevent timeouts, but the timer check was not working properly.
    If you want to try it ahead of time, you can grab the latest code from here: https://downloads.wordpress.org/plugin/ewww-image-optimizer.zip

    Thread Starter PrajwalDesai

    (@prajwaldesai)

    To scan around 4000 images, it took 1.5 hours. Why don’t you revert back the code to previous 2 versions when it was working fine ?.

    Thanks,
    PD

    Thread Starter PrajwalDesai

    (@prajwaldesai)

    After the scan it showed 855 images. After optimizing it shows Optimized 921/855. Why 921 images ?.

    Plugin Author nosilver4u

    (@nosilver4u)

    The 921 vs 855 is likely because your database is slow, or has some replication lag. Right after the last images are sent to the database, EWWW checks to see how many total images were queued. It is entirely possible for the last batch of scanned images to not be included in the count if the last INSERT/UPDATE transaction is not completed in the database yet.

    As for why the new scanner, there are a lot of reasons, but the main thing is a tradeoff between accuracy of the image counts and scanning speed. Overall, if you account for scanning time + optimization time, the new process should be faster. In your case, it probably isn’t a huge difference. On my server, with 40,000 images, the difference is staggering. It takes about a minute to scan that number of images. And then I only have a handful of images to process through the optimizer which might take 5-10 minutes, but worst case, if I had a thousand images like you did, it might take a half hour via the API. With the old process, it had to run through all 40,000 attachments, which meant 40,000 AJAX requests, and it took days, even when most of them had already been optimized.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Scan did not complete, will try again’ is closed to new replies.