Repository navigation
Conversation
tskisner
force-pushed
the
faster_sqlite
branch
from
October 24, 2024 16:59
a270849 to
31c4536
Compare
tskisner
force-pushed
the
faster_sqlite
branch
from
February 25, 2025 16:51
31c4536 to
24c6d27
Compare
tskisner
marked this pull request as ready for review
February 25, 2025 19:12
tskisner
marked this pull request as draft
June 12, 2026 16:15
…n in read-only case.
tskisner
force-pushed
the
faster_sqlite
branch
from
October 14, 2026 18:11
af65815 to
f2a467d
Compare
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
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.
This branch has some changes to explore sqlite performance through modifying low-level DB parameters. It currently includes some temporary timers that will be removed before review. Some starting test scripts for parallel read are in pwg-scripts, but I expect there will not be much noticeable change until considering the case of multiple readers plus a writer. Or perhaps there will be other non-sqlite bottlenecks identified.