PNI and Redis cache optimization #12470
Merged
Conversation
This file contains 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
danielfmiranda
approved these changes
Jun 10, 2024
There was a problem hiding this comment.
Thanks @robdivincenzo! Looking forward to having less "out of memory" errors. LGTM! 🚀
|
➤ Simon Acosta Torres commented: PR has been merged. |
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.
Description
This PR will remove memory-intensive custom template caching mechanisms from PNI (opting for standard PostgreSQL calls / rendition cache / Cloudflare caching instead) to free up Redis memory cache and correct "Out of Memory" errors.
Link to sample test page: https://foundation-s-tp1-557-12-r8pzre.herokuapp.com/en/privacynotincluded/
Related PRs/issues: #12243
To Test:
┆Issue is synchronized with this Jira Story