4 ms·
Good luck with that. A single Redis would not be able to serve that workload. Maybe a single machine but you're really pushing the limits there just with concur
by Xorlev 8y ago
Good luck with that. A single Redis would not be able to serve that workload. Maybe a single machine but you're really pushing the limits there just with concurrent TCP connections.
At that qps Redis has 2 microseconds per request.
I agree it caches well but your proposed architecture is definitely not production quality.
- gcbirzan 8y agoThere is a difference between queries and connections. With pipelining, a redis machine can easily serve that. If they stored things in a better structure, like a list, they'd easily be able to get that. On my machine 5 concurrent requests, at 100 items, it can do ~6 500 000 items per second, at 300, 11 000 000 per second, and it kind of caps out at that. Even with 1 concurrent connection, at 600 items, you get 6M per second.
- derptron 8y agoRedislabs has hardware recommendations[1] for production environments. Shouldn't be hard for devs to look it up and implement it. [1]https://redislabs.com/redis-enterprise-documentation/administering/designing-production/hardware-requirements/ https://redislabs.com/redis-enterprise-documentation/adminis...