3 ms·
When I was working at a large online travel website a few decades ago, we had a few hundred front-end boxes each with a connection pool set to (I think) around
by commandlinefan 6y ago
When I was working at a large online travel website a few decades ago, we had a few hundred front-end boxes each with a connection pool set to (I think) around 10 each - so around 2000 connections on the DB backend. We did some profiling and discovered that, under the heaviest load, we never had more than one connection active per web server (and usually 0), so a single shared DB connection would have been just as effective as the pool was.
- sudhirj 6y agoFor a read-only load, right? If there were writes and transactions I don’t see how that would work.
- commandlinefan 6y agoHm - it's been almost 20 years, so my memory is a bit hazy, but I seem to recall that there were (relatively infrequent) writes. But definitely no transactions: just grab a connection, insert/update some data, return it to the pool.
- abhishekjha 6y ago>But definitely no transactions: just grab a connection, insert/update some data Inserts/updates require transactions. How did you escape having transactions?