Skip to content

Clarify benchmark timing and measured work #7

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.

Sign up for GitHub

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

Merged
MugdhoAI merged 1 commit into from
Oct 10, 2026
Merged

Clarify benchmark timing and measured work #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,7 +141,7 @@ B tree pages use a compact fixed layout designed to keep the storage implementat

## Performance

The benchmark inserts 1,000 rows through the public table API and measures the insertion phase. It is intended for repeatable local comparisons rather than as a claim of production database performance.
The benchmark inserts 1,000 rows through the public table API, then flushes the database pages. It reports process CPU time from `clock()`, including both the insert loop and the flush but excluding database opening. It is intended for repeatable local comparisons rather than as a claim of production database performance.

The current write path keeps modified pages in the pager cache during inserts and persists them during an explicit flush. This avoids performing a file write and fflush for every inserted row.

Expand Down
Loading