Open
Conversation
e750072 to
94e2fdc
Compare
6b6e97c to
289e8c3
Compare
98caf29 to
b6046a9
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.
now that kaitai has serialization
we can use it to write sqlite pages
this is an early draft...
it only works to write the database header, no pages
further progress requires serializing pages
and writing them to the correct byte offsets in the database file
use case: convert a 5 GB jsonl file to sqlite
torrents_byteoffsets_parse_jsonl_zst.py
with my script i reach only 5 MiB/s
the bottleneck are the sqlite insert queries
my system (under load) can read and decompress at 20 MiB/s