Use connection pooling in sqlite backend #779

Merged
lx merged 2 commits from sqlite-r2d2 into main 2024-03-18 19:02:36 +00:00
Owner

Performance improvement by using several connections, instead of one big lock on the sqlite db for all threads. Several reads or reads + one write can go on simultaneously. Main benefit is that a long-going read such as a db snapshot no longer prevents all progress. Multiple writers still lock one another (like LMDB).

Performance improvement by using several connections, instead of one big lock on the sqlite db for all threads. Several reads or reads + one write can go on simultaneously. Main benefit is that a long-going read such as a db snapshot no longer prevents all progress. Multiple writers still lock one another (like LMDB).
lx force-pushed sqlite-r2d2 from 9122e8e5a1 to 4ee4e456a4 2024-03-18 16:23:18 +00:00 Compare
lx force-pushed sqlite-r2d2 from 4ee4e456a4 to 0cb6334658 2024-03-18 16:54:51 +00:00 Compare
lx force-pushed sqlite-r2d2 from 1426d2cec6 to efd1f4b05d 2024-03-18 17:05:32 +00:00 Compare
lx force-pushed sqlite-r2d2 from efd1f4b05d to b55f52a9b7 2024-03-18 17:31:55 +00:00 Compare
lx changed title from WIP: implement connection pooling in sqlite backend to WIP: Use connection pooling in sqlite backend 2024-03-18 17:45:56 +00:00
lx changed title from WIP: Use connection pooling in sqlite backend to Use connection pooling in sqlite backend 2024-03-18 19:01:55 +00:00
lx merged commit 1a0bffae34 into main 2024-03-18 19:02:36 +00:00
lx deleted branch sqlite-r2d2 2024-03-18 19:02:37 +00:00
Sign in to join this conversation.
No description provided.