Fix #32: Persistent SQLite connections#186
Open
bscholer wants to merge 2 commits into
Open
Conversation
- Add _persistence_conn attribute to JobManager and ProjectManager - Add _init_persistence_db() to initialize connection once - Add _get_persistence_connection() helper for both managers - Update all DB access methods to reuse the persistent connection - Run migrations once at startup instead of on every connect() - Add bench_persistence.py benchmark showing 100x+ speedup for scenarios with many job events (e.g. Siril's seq_register)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #32
This adds persistent SQLite connections to JobManager and ProjectManager,
savoiding the overhead of creating a fresh connection and running migrations
for every job/project persistence operation.
Changes
scenarios with many job events (e.g. Siril's seq_register)