bitactive

This patch has been merged for RedisCluster code, but analogous code has not been added for the standard Redis session handler. Is this an oversight or a deliberate action? In...

Hi, we are using QueuedTracking on 3 frontend servers, each with 24core and backend DB+redis with 128core+1TB RAM. We are tracking single website with billion of monthly pageviews. DB has...

@snake14 @AltamashShaikh Increased no of requests from 10 per batch to 25 per batch. Now each of 16 workers have ~80% CPU and increased total throughput (processed requests per second)...

@snake14 @AltamashShaikh Changing requests per batch to 50 gives another 10-15% throughput increase. Will try 100 soon as traffic increase. Meantime i have another question for this configuration. If i...

Our top rate is approximately 269 RPS * 16 workers, resulting in a total of 4300 RPS. This is on a machine with 128 high-clock cores, 1TB of RAM, and...

From our experience, RTT between workers, Redis, and the database can significantly impact RPS. This is why we use multiple frontend nodes but run workers, the database, and Redis on...

@AltamashShaikh I think that your solution with ``` protected function getQueueIdForVisitor($visitorId) { $id = ord ($visitorId); return $id % $this->numQueuesAvailable; } ``` will not work because ord() will return the...

@AltamashShaikh In real world scenario @haristku works quite well when we have random distribution of VisitorIds. However your approach is better and will better work in edge cases like one...