About Database Connection Pool Sizing

Re:About Database Connection Pool Sizing by commandlinefan on Monday November 12, 2018 @10:15AM (#18433046)

I did some profiling when I was working at one of the big online travel sites. We were running about 300 or so servers with a 50-connection pool each. After testing, we determined that at no time, ever, was more than one connection in simultaneous use across the server farm. We could have reduced it to a single shared connection per server and maintained the same QoS.

[ Parent | on HN ]

Re:About Database Connection Pool Sizing by nextweek2 on Tuesday November 13, 2018 @02:44AM (#18439366)

I've always worked with a transaction per connection principle to saving having to manage transaction id's within a connection.

Were you not using transactions or did you have some other approach?

[ Parent | on HN ]