-
Notifications
You must be signed in to change notification settings - Fork 3
added note to redis limits #50
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
base: main
Are you sure you want to change the base?
Conversation
Clarified storage limit information for Redis usage.
Removed redundant note about exceeding storage limit and consolidated advice on staying under the limit.
| If your app exceeds 500 MB of storage, writes to Redis may fail, which can affect features that depend on cached or stored data. To stay under the limit: | ||
|
|
||
| - Evict data by removing keys you no longer need | ||
| - Use TTLs to set expirations for temporary or stale data | ||
| - Monitor your app's data usage and be selective about what you store | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is the only "real" diff in the file, and the rest is just style tweaks?
Can we get some sort of style enforcement on this repo, and do one big "style tweaks only" PR to bring the whole repo up to code? It's really hard to read a PR with 300 lines of diff, when there's only 5 that are "real changes" :\
|
|
||
| If your app exceeds 500 MB of storage, writes to Redis may fail, which can affect features that depend on cached or stored data. To stay under the limit: | ||
|
|
||
| - Evict data by removing keys you no longer need |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How possible is this with our current architecture?
Closes #
πΈ TL;DR
π Details
Design Doc
Jira
π§ͺ Testing Steps / Validation
β Checks