News for hackers. Stuff that matters.

A comment on About Database Connection Pool Sizing. Parent comment

Re:About Database Connection Pool Sizing by derefr on Monday November 12, 2018 @03:54PM (#18435695)
> There's definitely ways to handle that better than O(N), at least in the average case.

O(N) root-level snapshot objects of the state, I mean. Like O(N) git commits. The minimum size of the persisted MVCC snapshot data, probably just scales with O(log N) of the number of connections, depending on what sort of data structure you're using for copy-on-write'ing your snapshots.

[ Parent | on HN ]
Re:About Database Connection Pool Sizing by anarazel on Monday November 12, 2018 @04:01PM (#18435779)
Most databases don't have "root level snapshots of the state" in the way you appear to imagine them. Leaving trivial per-transaction information ('did this transaction id commit', ~a few bits per xact) aside, usually it won't scale with the number of snapshots, but with the amount of change done by writing transactions.
[ Parent | on HN ]