tursodatabase/turso

Don't drop whole page cache on rollback

Open

#4,546 opened on Jan 9, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (1,001 forks)github user discovery
help wantedperformance

Repository metrics

Stars
 (19,103 stars)
PR merge metrics
 (Avg merge 2d 11h) (147 merged PRs in 30d)

Description

We drop the whole page cache on rollback because it's obviously safe. But it's also obviously slow for any workload that does rollbacks often enough.

Contributor guide

Research direction
Study the page cache module and identify how rollback currently drops the entire cache. Explore incremental cache invalidation mechanisms, such as tracking dirty pages or using a write ahead log (WAL) to only invalidate affected pages.
Tech stack
rust
Domain
databasebackend
Issue type
Performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustSQLite internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50