Use connection pooling in sqlite backend #779
No reviewers
Labels
No Label
AdminAPI
Bug
Check AWS
CI
Correctness
Critical
Documentation
Ideas
Improvement
Low priority
Newcomer
Performance
S3 Compatibility
Testing
Usability
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#779
Loading…
Reference in New Issue
No description provided.
Delete Branch "sqlite-r2d2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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).
9122e8e5a1
to4ee4e456a4
4ee4e456a4
to0cb6334658
1426d2cec6
toefd1f4b05d
efd1f4b05d
tob55f52a9b7
WIP: implement connection pooling in sqlite backendto WIP: Use connection pooling in sqlite backendWIP: Use connection pooling in sqlite backendto Use connection pooling in sqlite backend