Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change sqlite journal mode to WAL #5213

Merged
merged 3 commits into from
Dec 16, 2024
Merged

Change sqlite journal mode to WAL #5213

merged 3 commits into from
Dec 16, 2024

Conversation

dynco-nym
Copy link
Contributor

@dynco-nym dynco-nym commented Dec 4, 2024

This change is Reviewable

@dynco-nym dynco-nym added this to the Reeses milestone Dec 4, 2024
Copy link

vercel bot commented Dec 16, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
docs-nextra ⬜️ Ignored (Inspect) Visit Preview Dec 16, 2024 2:41pm
nym-next-explorer ⬜️ Ignored (Inspect) Visit Preview Dec 16, 2024 2:41pm

@dynco-nym dynco-nym merged commit b4f51ba into develop Dec 16, 2024
15 checks passed
@dynco-nym dynco-nym deleted the dz-sqlite-wal branch December 16, 2024 15:40
@tommyv1987
Copy link
Contributor

Testing Completion Report: SQLite WAL Mode Implementation
Completion Date: 13/01/2025

Overview:
The update enables SQLite Write-Ahead Logging (WAL) mode across internal modules such as client-core, gateway-storage, and nym-api to improve database performance during concurrent read/write operations

Key configuration changes include enabling WAL mode, SqliteSynchronous::Normal, and SqliteAutoVacuum::Incremental. Testing confirmed compatibility with existing data, proper initialisation of new databases, and improved throughput in high-load scenarios

No issues were identified during testing

Impact: Better database performance and maintenance efficiency for internal tools

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants