Erase Optimization History – 724350 entries

  • Resolved enkirch

    (@enkirch)


    1 year, 3 months ago

    Hi ,
    our website currently has 724350 images optimized.

    And every single image is stored in the database. So there are 724350 entries in the database, right?

    Now if a new image is to be optimized, this new image must be matched with each of the 724350 entries, correct?

    I think the plugin is having problems with this on our end. It seems to no longer opitimize the images via cronjob.

    We have now programmed it to create a text file with the new folder paths and then load this text file in wp-config and assign it to the plugin via “EWWW_IMAGE_OPTIMIZER_AUX_PATHS”.

    So now my question. There is a button “Erase Optimization History”. I guess, this will empty the database with the entries. ( Is this the database table “ewwwio_images” ?)

    What exactly happens when I press the button? Does a modal come up where you can follow the process of emptying?

    And can I expect, if I empty the 724350 entries, that the plugin will run faster again ?

    Because calling the settings page in the admin also already takes several seconds.

    Of course you would have to make sure that already optimized images, folder paths are defined in the exclude, that these are not optimized again.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter enkirch

    (@enkirch)

    Ok we have deleted the entries now. Despite the amount of images, it only took a few seconds to clear the table.

    Also worth noting. Before the mass optimizer needed for 1 image (jpeg) about 4-5 seconds.

    Now one image needs about 0.5 – 1 second.

    Plugin Support adamewww

    (@adamewww)

    There is a table, if you are using Scheduled Optimization, which it seems may be the case, that is going to scan that folder every hour and check the 724K files against the database, which is what is going to take a while. Then, if it doesn’t finish in an hour and doesn’t process any new images, it’s going to cancel the process and start over. That could be the slowdown that you were seeing.

    Thread Starter enkirch

    (@enkirch)

    Hi,
    yes we are watching the whole thing now. And look every few hours of these values

    There are 5,932 images optimized so far.
    Current status of the queue: busy
    Currently there are 109 images in the queue.

    One question I have.
    Why are images in the queue and not optimized?
    A jpeg takes about 1 second, so that would be about 2min. Why were these images not optimized during the last cronjob call?

    Thread Starter enkirch

    (@enkirch)

    Is there a maximum time period in which images are optimized ?

    I just restarted the cronjob myself several times and at some point there were images in the queue that were optimized.

    Then it stopped. And then it continued?

    Does this also have something to do with the cronjob “wp_ewwwio_image_optimize_cron” and “”ewww_image_optimizer_auto”.

    I’m sure I’ve only seen one of each for the past few weeks?

    Plugin Support adamewww

    (@adamewww)

    I believe this was resolved in that something was stuck in the queue (as discussed in a direct email). We can continue the conversation there.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Erase Optimization History – 724350 entries’ is closed to new replies.