Firstly, don't use KEYS, SCAN if you must.
Secondly, both the-command-that-should-not-be-used and SCAN iterate through your server's entire keyspace. This will always result degraded performance as the number of total keys grows.
The way you'd usually keep track of key names in Redis (to quickly retiring these names) is by managing a set who's members are the relevant key names. This requires you to SADD/SREM accordingly in your code whenever you create/delete a key that belongs to that "index" set.
--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+u...@googlegroups.com.
To post to this group, send email to redi...@googlegroups.com.
Visit this group at http://groups.google.com/group/redis-db.
For more options, visit https://groups.google.com/d/optout.
^retiring^retrieving