3 ms·
120GB on a single thread, yeah. Redis has been abused for quite some time but 120GB is way out of reasonable reach for current CPU arch if you use a single core
by xxs 9y ago
120GB on a single thread, yeah.
Redis has been abused for quite some time but 120GB is way out of reasonable reach for current CPU arch if you use a single core only (even if you switch off hyper threading)
- iagooar 9y agoCall me a slowpoke, but I wasn't aware that Redis was single core!
- lozenge 9y agoIt makes it great for storing distributed locks, semaphores, and thanks to Lua scripting it can store/update cache invalidation lists - eg https://github.com/Suor/django-cacheops https://github.com/Suor/django-cacheops
- deleted 9y ago[deleted]
- jackmott 9y agojust randomly curious here - why? hash time gets absurd?
- ihsw2 9y agoPresumably, time complexity for most operations correspond directly with CPU usage. See here for an example with RPUSH: https://redis.io/commands/rpush https://redis.io/commands/rpush RPUSH is O(1) which the best you can possibly get. ZADD on the other hand is O(log(n)), which is quite good but at a large scale it becomes easier to run into performance limitations, especially on high workloads. Performing O(n) operations on large data sets is out of the question unless you're comfortable with Redis being unavailable for multiple seconds/minutes. That said, you will have to limit yourself to operations that are computationally simple (ie: O(1) or O(log(log(n))) or pre-shard across multiple instances (or run a Redis cluster).
- rhizome 9y agoRedis on MOSIX might be an interesting experiment.