Benchmarks: ThrustDB thread_pool_hybrid vs MySQL Enterprise Edition thread_pool

So previously we’ve seen my thread pool, hybrid versus connection per thread handler and mine is lighter weight, faster and more scalable. But what about against the Enterprise-edition thread pool connection handler? The one you can’t get the source for and must pay licensing fees to run it in production?

A little background: I wrote the first version of that enterprise thread_pool way back in 2006-07 when I worked for MySQL AB. And it was a significant advance in that that it allowed so many more connections, but the code was a lot slower on low connection counts. Also as that was nearly 20 years ago and it’s been sold as close source since (it was the first close source server side component ever sold by MySQL). It was also one of the things MySQL AB was contractually obligated to produce before Sun Microsystems would purchase MySQL. Idk why, and I wasn’t told it, but it was made clear to me that this was very important code.

Anyway how does my thread pool evented Io connection handler benchmark against this nearly 20 year old thread pooled evented io connection that is “Enterprise” ready?

Pretty damn good.

ThrustDB’s thread_pool_hybrid connection handler beats the MySQL Enterprise edition thread_pool across the board and is also significantly more scalable. See the graphs: thread_pool_hybrid_vs_enterprise_thread_pool-mysql-9.0.3-redhat_9.0.4-r7i.4xlarge.md