Benchmarks: Sweep accdb Cache Footprint and Min Reserved - #11437
Benchmarks: Sweep accdb Cache Footprint and Min Reserved#11437MilanSuri wants to merge 4 commits into
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
The benchmark must distinguish cache hits from accounts found.
Get a fresh assessment by requesting another Copilot review.
Pull request overview
Adds configurable accdb benchmark setup and replay sweeps for cache footprint and minimum-reserved settings.
Changes:
- Parameterizes cache and replay configuration.
- Adds cache footprint and minimum-reserved sweeps.
- Cleans up benchmark allocations between runs.
File summaries
| File | Summary | Review |
|---|---|---|
src/flamenco/accdb/bench_accdb.c |
Implements configurable benchmark setup and cache sweeps. | The 36.8% metric reports accounts found, not cache hits; instrument cache source or rename the metric. Moderate, 3 votes. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite (auto)
Note
Copilot is running an experiment and ran this review at Lite.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| tombstone (realistic for hot accounts like token program, | ||
| system program, fee payers, etc.). */ | ||
| ulong pubkey_pool_sz = writes_per_slot * 4UL; | ||
| ulong pubkey_pool_sz = writes_per_slot * slot_cnt; |
There was a problem hiding this comment.
Yeah I found this issue as well, I changed the pubkey_pool_sz from writes_per_slot * 4UL to being writes_per_slot * slot_cnt because I needed a way of increasing cache pressure for each sweep.
Is there a way to get the true cache hit rate in the Firedancer codebase or would it be better to just rename it to like found rate?
Added benchmarks to sweep:
Used to investigate memory/performance tradeoffs in different cache configs.
Output of the Sweeps:
Note
I think the hit rate is being calculated incorrectly but wasn't sure if you had any recommendations for correcting how it's calculated.