4 ms·
> That's only true if your transactions are all busy most of the time. And this is actually what you want from a performance point of view: Reduce the number o
by taffer 8y ago
> That's only true if your transactions are all busy most of the time.
And this is actually what you want from a performance point of view: Reduce the number of roundtrips and keep your transactions as short as possible.
Once a transaction locks a row or table, the lock persists regardless of whether the transaction is active or inactive, resulting in resource contention. The same applies to memory: if each connection has 10 MB of memory, 10 GB of memory is wasted for every 100 unused connections that could otherwise have been used for caching.
- anarazel 8y ago> And this is actually what you want from a performance point of view: Reduce the number of roundtrips and keep your transactions as short as possible. Uhm, obviously. But it turns out there's other constraints too. Like whether optimizing for that to a significant degree in each application is worthwhile and/or realistically being done. And latency is a thing either way. It's extremely rare to not have briefly idle connections in OLTP context, even more so if the app code isn't heavily optimized for it (but even if).