Schedule Option Handler Purges#125
Merged
wpscholar merged 1 commit intobluehost:masterfrom Feb 4, 2025
Merged
Conversation
geckod22
approved these changes
Feb 4, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed changes
Story: https://jira.newfold.com/browse/PRESS7-124
In cases of option updates, the option handler was processing a large number of concurrent updates, which overloaded the server with requests because the throttle could not intervene quickly enough. This PR introduces a WP Cron event that is scheduled whenever an option update occurs. The event triggers a single cache purge 60 seconds later, preventing multiple requests from overwhelming the server at once.
epc_purge_scheduled.mp4
Type of Change
Checklist
Further comments