Skip to content

Conversation

aldy505
Copy link
Collaborator

@aldy505 aldy505 commented Aug 13, 2025

Caution

This is me playing around with Valkey as a Redis replacement, since so many people from the community mentioned Valkey already.
There is no guarantee that this will be merged at all.

Copy link

codecov bot commented Aug 13, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.45%. Comparing base (e4d311b) to head (89d2ed9).
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3868   +/-   ##
=======================================
  Coverage   99.45%   99.45%           
=======================================
  Files           3        3           
  Lines         183      183           
=======================================
  Hits          182      182           
  Misses          1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@hubertdeng123
Copy link
Member

It's nice to experiment with this, but could cause some pain for us to maintain self-hosted since prod uses redis

@aldy505 aldy505 mentioned this pull request Aug 23, 2025
1 task
@frederikspang
Copy link
Contributor

While valkey is a great replacement - I think Redis 8 should be the natural next-step - We're running redis:8.0.2-alpine in prod; And we're seeing no problems there. We could try tuning for io-threads for throughput?

I haven't measured how much throughput is actually in Redis, by default (vs kafka vs postgresql for instance).

But if Celery + rate limits + something-else is running there, there must be some.

I can test out 8.2 with increased io-threads over the next few weeks in our prod.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

3 participants