This Thread had not been rated yet
The Redis Connection Handler is an alternative to the default MySQL based connection handler which utilises a multithreaded fork of the Redis software named KeyDB to accelerate connection creation on load balancers while ensuring no connection to MySQL is made during the process which is the bottleneck for most streaming services once they reach a certain size.
The alternative handler is recommended for any service that has more than 10,000 concurrent connections to achieve maximum performance, although it is not an absolute requirement unless you run into issues where MySQL is using most of your CPU trying to handle the incoming traffic, something to be mindful of.
Pros
Some of these drawbacks may be too much for some users to handle and could also diminish the administrative experience to an extent, however if you're in the realm of 50k, 100k, 200k concurrent connections you'll be thankful to have this functionality available when every other system shits the bed trying to keep up with the throughput.
The alternative handler is recommended for any service that has more than 10,000 concurrent connections to achieve maximum performance, although it is not an absolute requirement unless you run into issues where MySQL is using most of your CPU trying to handle the incoming traffic, something to be mindful of.
Pros
- Significantly more concurrent connections per CPU instruction
- Faster zap times
- Combine with Caching System to achieve 0 mysql usage for ALL client-facing connections
- Fast load times for Live Connections page
- Multithreaded
- No connections are synchronised to the database, so limited recovery when RAM is cleared (on reboot / service restart)
- Reduced search and ordering functionality in the Admin / Reseller panel due to no MySQL calls being made, all information is live in Redis
- Can only sort by Start Date ascending / descending in Live Connections page
- Still a work in progress, however functionally complete and stable, more features will become available in the future
Some of these drawbacks may be too much for some users to handle and could also diminish the administrative experience to an extent, however if you're in the realm of 50k, 100k, 200k concurrent connections you'll be thankful to have this functionality available when every other system shits the bed trying to keep up with the throughput.
This Thread had not been rated yet
