Showdown: MySQL 8 vs. PostgreSQL 10

Re:Showdown: MySQL 8 vs. PostgreSQL 10 by nvivo on Wednesday May 23, 2018 @01:33PM (#17136108)

I had some real issues with mysql handling more than 2000 connections. Once past that limit, cpu usage increases exponentially with few connections due to context switching. At 3000 connections, 80% of thr cpu was used gor context switching and it got unusable. That was a 64 core/256gb ram server.

[ Parent | on HN ]

Re:Showdown: MySQL 8 vs. PostgreSQL 10 by stevenwoo on Wednesday May 23, 2018 @03:16PM (#17137205)

What did you do to address the mysql connection problem?

[ Parent | on HN ]

Re:Showdown: MySQL 8 vs. PostgreSQL 10 by nvivo on Wednesday May 23, 2018 @06:11PM (#17138844)

I ended up reducing the number of clients. In my case I had a thousand servers, and I was able to change the application structure and merge them into a dozen big application servers. Now with connection pooling each server has less than 100 connections.

As a more permanent solution for scaling, I'm moving out of mysql into something more distributed.

[ Parent | on HN ]

Re:Showdown: MySQL 8 vs. PostgreSQL 10 by kolzeq on Friday May 25, 2018 @08:25AM (#17152897)

Or you can have move to mariadb, using configuration "thread_handling=pool-of-threads" to enable threadpool that is exactly the solution.

(MySQL have that only for "entreprise" version)

[ Parent | on HN ]

Re:Showdown: MySQL 8 vs. PostgreSQL 10 by ngrilly on Friday May 25, 2018 @04:38PM (#17157739)

Something more distributed like what?

[ Parent | on HN ]