Repository navigation
chore(example): benchmark app workloads and Drizzle - #470
Merged
Merged
Conversation
Add WAL-mode cases modeled on app workloads: a chat app that stores synced messages, browses its inbox and conversations, and launches, plus key-value storage, a JSON response cache, and a BLOB thumbnail cache. The chat sync and browse cases also run through Drizzle. Add async point lookups, executeRaw arrays, and synchronous inserts in one transaction. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
chrispader
added a commit
that referenced
this pull request
Oct 29, 2026
Port the app workload cases from #470: a chat app that stores synced messages, browses its inbox and conversations, and launches, plus key-value storage, a JSON response cache, a BLOB thumbnail cache, async point lookups, and synchronous inserts in one transaction. The Drizzle and executeRaw cases stay out because this branch has neither API yet. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch was previously deployed
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.
Most benchmark cases time one API call at a time on SQLite's default rollback journal, so the write cases mostly measure disk syncs. Apps usually turn on WAL, run several small async queries per screen, and often query through an ORM, but only the mixed case uses WAL and no case uses an ORM. This adds cases modeled on app workloads, all in WAL mode with
synchronous = NORMAL, and cases for API calls the suite didn't cover. Existing cases keep their order and labels.executeRaw, and synchronous inserts inside one transaction.🤖 Generated with Claude Code