История изменений
Исправление leave, (текущая версия) :
http://redis.io/topics/benchmarks
With high-end configurations, the number of client connections is also an important factor. Being based on epoll/kqueue, the Redis event loop is quite scalable. Redis has already been benchmarked at more than 60000 connections, and was still able to sustain 50000 q/s in these conditions. As a rule of thumb, an instance with 30000 connections can only process half the throughput achievable with 100 connections.
Нет, конечно, хозяин-барин, можете и липкие сессии использовать.
балансировка по ап решает эту проблему
и добавляет новых :D
Исходная версия leave, :
http://redis.io/topics/benchmarks
With high-end configurations, the number of client connections is also an important factor. Being based on epoll/kqueue, the Redis event loop is quite scalable. Redis has already been benchmarked at more than 60000 connections, and was still able to sustain 50000 q/s in these conditions. As a rule of thumb, an instance with 30000 connections can only process half the throughput achievable with 100 connections.
Нет, конечно, хозяин-барин, можете и липкие сессии использовать.