3 ms·
Maybe. Kinda. Not really. You can have an awful implementation of a connection pooler, sure, but opening an authenticated socket is more expensive by far than
by dijit 7y ago
Maybe. Kinda. Not really.
You can have an awful implementation of a connection pooler, sure, but opening an authenticated socket is more expensive by far than just referencing one.
Less so for a unix socket/named pipe- but still much slower than a memory lookup.
Of course you probably don’t care until you hit a certain scale or number of backend system accesses.
- johannes1234321 7y agoFetching a connection from a (sane) pool isn't just a memory lookup. Database conenctions have to be cleared of state (transactions, temp tables, prepared statement handles, ...) which takes time as well. Otherwise one runs into "funny" bugs at some point in time.