Prevent PropertBag from being so noisy about deprecation warnings #16390
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.
Overview
Turns out calling
Civi::log()
can be problematically slow (like taking over 0.5s/call) on some hosting environments. Currently there's a lot of core that is not updated to useCivi\Payment\PropertyBag
yet, and that class was deliberately built to make noise about this. This resulted in a problematic performance hit for sites with slow logging.See https://chat.civicrm.org/civicrm/pl/c9bwzmtrg7dhircfyfei5fezge
Before
PropertyBag would emit
Civi::warning()
synchronously every time it encountered deprecated use.After
PropertyBag now stores all these complaints up and registers a shutdown function to write them to the log in one go.