-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Purge taking too much time while editing a Post #257
Comments
@thecancerus looks like you are using WordOps for that https://community.wordops.net/ is the right place to look for support. Since EE v4, we strongly recommend using Redis for full page cache. Still, I will give a wild shot based on your use of You can try disabling the archive purge option (if its enabled) |
@rahul286 thanks, we were using the purge archive settings. I will also explore the Redis cache and see how it goes. |
Redis uses Lua so purging is very fast ➞ https://github.com/rtCamp/nginx-helper/blob/master/admin/class-predis-purger.php#L249-L258 You can uncheck archive checkboxes until you shift to redis-based full page cache. |
We need to purge archives as well, so for now we have modified the plugin to insert the URLs in a queue instead of doing a real-time purge, then handled the purge using cron. Checking the dev setup with Redis Cache, we already use Redis for other things, mostly we will also move to Redis cache from |
I would suggest this fix. But the repository seems private, I can't commit.
|
WordPress/wordpress-develop#3022 should help with this. |
When editing a post with multiple tags and categories attached to it, it takes lots of time to update. Sometimes it can take more than a minute. When I investigated, I found that most of the time was taken in the purge requests ( anywhere between 500ms to 1.3seconds per request).
My Setup
WordPress 5.7, Nginx (based on WordOps), WPFC cache with PHP 7.4.
Server: AWS t2.xlarge, OS ubuntu 20.04
Neingx helper plugin version 2.2.2
The site is behind Cloudflare
The text was updated successfully, but these errors were encountered: