wp_options table filling with wp_swcfpc_cache_preloader records

Hi Dan,
these records are automatically added from WordPress for batch processes like the preloader.

If you don’t want use the preloader, just disable the option to automatically preload pages purged from Cloudflare, under PRELOADER section.

Have a nice day! ??

To confirm my understanding: if I continue to use the preloader, I should expect to see wp_options to fill up with batch process records. Is that correct?

Hi @dannoll ,
yes and no. The preloader uses the following library:

https://github.com/deliciousbrains/wp-background-processing/blob/master/classes/wp-background-process.php

When a new queue (the list of URLs to preload) is created, a new “_batch_” record is added into the wp_options table together with some transient.

When the queue becomes empty, the library deletes the “_batch_” record (code lines 317-322):

// Update or delete current batch.
if ( ! empty( $batch->data ) ) {
	$this->update( $batch->key, $batch->data );
} else {
	$this->delete( $batch->key );
}

If you keep seeing those records at the end of preloading, something went wrong with the library. Sometimes I happened to see them disappear on the next preloading task.

I notice several hundred records for the same post — that is, whose “Option Value” in the wp_options table is exactly the same. Is this expected? NOTE: This occurs for a few posts.

P.S. Thanks for your prompt replies, and for your work on an excellent plugin.

Hi @dannoll ,
on 4.3.2 I added a lock system in order to execute only 1 preloader at once. This will save cpu and will add less records in wp_option table.

I suggest you to update to latest version

Thank you. I just downloaded it and am running it. I will keep you posted.

Also — should I assume this plugin update will clean or trash collect the old duplicate records the plugin created in wp_options?