Moving Posts to Trash Slow Unless Cache Disabled and Enabled Again

Hi @macksix,

Do you have object cache on these websites? Or just enabled page cache only?

Moving a post to the trash can take a long time on large WordPress setups. However, 15 seconds still seems unreasonable.

Can you try this snippet and let me know if it makes any difference:

add_filter( 'powered_cache_advanced_cache_purge_urls', function ( $urls, $post_id ) {
	$urls   = array();
	$urls[] = get_permalink( $post_id );
}, 10, 2 );

When a post is moved to trash, Powered Cache deletes the cache for the pages associated with that post. (such as post type archive, category, author etc..) I’m curious if it causes the delay.

Hi @macksix,

Thanks for the feedback.

Adding that code in a child theme function.php makes a post move to trash and restore faster.

Note that, not only is the slowness on moving to trash, it is also slow at restoring from the trash.

The same cache invalidation process works whether you move to a post to trash or update an existing public post. We will consider how to make this cache invalidation process faster (or make it async). Meanwhile, you can keep the snippet on your websites.

Also, I do not have Object cache turned on.

Can you tell me more about the hosting environment? Especially what kind of disks running on the server?

Based on our tests with SSD disks, it doesn’t cause a huge delay in deleting all related page’s cache from the server. That process can be slow on HDD disks.

That’s odd. It shouldn’t be such a problem with NVMe.

Thanks for the info. I’ve created an issue about this (in case you want to follow)

How many posts do you have? and Is the cache preloading enabled on your website?

Actually, it would be better if you can export the configuration file and share it with us via support@poweredcache.com.

Unfortunately, it’s not easy to reproduce this issue on our end. This is why we need additional info.

I am a bug hunting and report expert, so I don’t mind at all. 🙂

Thanks a lot, appreciated it 🙂

Marking as resolved. Feel free to re-open it if the problem persists.