bench(pk): add --pk-default (pure default DatabaseConfig) and publish honest default-config numbers (P3) - #385
Merged
Conversation
… honest numbers New harness mode runs the fair-PK comparison where the SharpCoreDB arm uses a PURE default DatabaseConfig (NoEncryptMode=false; no page-cache/durability/ insert harness flags) vs SQLite, median of 3. Honest result (recorded in docs/benchmarks/default-config-pk.md): the default path DOES engage the Columnar fixed-width fast paths (counters verify) but UPDATE/DELETE land at ~84K/~93K ops/s (~3.5x/~4.2x behind SQLite) vs ~245K/~172K with the tuned harness config. The dominant cause is the default WalDurabilityMode.FullSync per-commit flush; the safe default is kept, with the follow-up being an optimized synchronous commit flush (re-run this harness to gate the release-cut at <= ~2x).
|
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
1 participant
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.
Samenvatting
P3: eerlijke default-config benchmark gepubliceerd +
--pk-defaultharness-mode.--pk-defaultdraait de fair-PK-vergelijking waarbij de SharpCoreDB-arm eenpure default
DatabaseConfiggebruikt (NoEncryptMode=false, géén harness-only knoppen) —alleen de engine is gepind. Median-of-3 per fase.
docs/benchmarks/default-config-pk.md):DefaultEngineSelectionTests), maar de throughput blijft achter op de getunede config(~245K/~172K) — dominant door de default
WalDurabilityMode.FullSyncper-commit flush.optimaliseren en deze harness als gate voor de release-cut gebruiken (doel ≤ ~2x).
Validatie