News for hackers. Stuff that matters.
Re:SSL Performance Overhead in MySQL by HarrisonFisk on Thursday October 10, 2013 @02:18PM (#6529243)
In addition, when you are dealing with many thousand application servers and many hundred database connections, the database will not end up happy having to maintain > 10k connections.

So you will end up needing to add a proxy or connect every time. As you indicated, since MySQL connections are so cheap (ie. you can do > 50k per second), it is faster and easier to create a new connection each time.

Re:SSL Performance Overhead in MySQL by falcolas on Thursday October 10, 2013 @02:26PM (#6529279)
Not just the database, at those quantities of connections, the OS itself starts to have problems.

One frequently implemented solution is to kill off old idle connections, but you may be surprised at how many pooling solutions don't deal with killed connections well (or force the handling on the application at the wrong layer of abstraction).

Re:SSL Performance Overhead in MySQL by jrochkind1 on Thursday October 10, 2013 @10:32PM (#6531161)
> it is faster and easier to create a new connection each time.

Unless you're creating an SSL connection, right?

Did you guys read the same OP I read?