2 ms·
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 t
by commandlinefan 8y ago
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.
- nextweek2 8y agoI'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?