feat: compress sqlite db#2278
feat: compress sqlite db#2278MasterPtato wants to merge 1 commit into03-26-feat_graceful_worker_shutdownfrom
Conversation
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
How to use the Graphite Merge QueueAdd the label merge-queue to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
There was a problem hiding this comment.
PR Summary
This PR adds SQLite compression using lz4_flex and updates snapshot, key, error, and metric handling in our pools module, while also refining logging in runtime shutdown and actor routes.
• Added lz4_flex dependency (v0.11.3) and updated snapshot logic in packages/common/pools/src/db/sqlite/mod.rs to compress and chunk database files.
• Introduced CompressedDbDataKey/CompressedDbDataChunkKey in packages/common/pools/src/db/sqlite/keys.rs and a new COMPRESSED_DATA constant in packages/common/fdb-util/src/keys.rs.
• Added new Lz4 error variant in packages/common/pools/src/error.rs and new upload/download metrics in packages/common/pools/src/metrics.rs (verify naming conflicts).
• Adjusted flush handling in chirp-workflow to log failures without forcing shutdown.
• Enhanced runtime shutdown observability in packages/common/runtime/src/lib.rs.
10 file(s) reviewed, 2 comment(s)
Edit PR Review Bot Settings | Greptile
Deploying rivet with
|
| Latest commit: |
910b7c0
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://22e3b801.rivet.pages.dev |
| Branch Preview URL: | https://03-27-feat-compress-sqlite-d.rivet.pages.dev |
dee60d0 to
2c0ca5c
Compare
2c0ca5c to
910b7c0
Compare
Merge activity
|
<!-- Please make sure there is an issue that this PR is correlated to. --> ## Changes <!-- If there are frontend changes, please include screenshots. -->

Changes