Cronjob Optimisation – Scan Methode

As you may have noticed, the Bulk Optimizer scan has 2 different “stages”. The first uses a function that checks items in the Media Library, while the second is a different function that does a recursive scan of files in any given folder.

The Scheduled Optimizer that runs via wp_cron uses the latter function. Does that answer your question?

OK, I’ll try to explain it another way.

we have 100000 images approx.

The current plan is to optimise them with the mass optimiser gradually over the next few weeks.

Unfortunately the cronjob does not start, probably because there are too many pictures.

If I now

define( ‘EWWW_IMAGE_OPTIMIZER_SCAN_MODE_B’, true );

would this apply to the mass optimiser and the cron job optimiser or only to the mass optimiser.

I currently manage about 1500 images per hour with the Massen Optimerer. Is there anything else I can do?

• This reply was modified 1 year, 8 months ago by enkirch.

Scan mode B does affect both, as it impacts how the plugin checks whether any given image has been optimized. It is intended to conserve memory and is slower as it has to do a db query for every single file that it checks. But given how many images you have, that’s going to be unavoidable, so you might as well define it.

Since you’re planning to use the bulk optimizer initially, the cron job optimizer shouldn’t be enabled until you are completely done.

1500/images an hour is pretty good, and no there isn’t any way to speed it up.