You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using nitter and redis as docker containers and I could see that for some users it wasnt fetching tweets for more than 1.5 years because it was disabled as per redis caching due to errors. Do we have any specific config for redis caching which needs to be set regarding flushall or flushdb or TTL etc ?
The text was updated successfully, but these errors were encountered:
This is a bit tricky since stock Redis doesn't allow per-field TTL for hashes. The cache saves ~0.25 seconds per profile load, so it's a huge saving in terms of bandwidth, load time, and API usage. I'll have to think about this again and see if I can figure something out.
For now, the only advice I have is to run redis-cli flushdb every now and then, maybe throw it in a cronjob.
zedeus
changed the title
redis caching
Redis caching outdated username->id pairs
Feb 27, 2025
I am using nitter and redis as docker containers and I could see that for some users it wasnt fetching tweets for more than 1.5 years because it was disabled as per redis caching due to errors. Do we have any specific config for redis caching which needs to be set regarding flushall or flushdb or TTL etc ?
The text was updated successfully, but these errors were encountered: