Skip to content

Extend DB benchmark to support state store (SS) backends#2995

Open
Kbhat1 wants to merge 7 commits intomainfrom
state-store-db-benchmark
Open

Extend DB benchmark to support state store (SS) backends#2995
Kbhat1 wants to merge 7 commits intomainfrom
state-store-db-benchmark

Conversation

@Kbhat1
Copy link
Contributor

@Kbhat1 Kbhat1 commented Feb 28, 2026

Describe your changes and provide context

  • Extend cryptosim DB benchmark to support state store (SS) backends via a lightweight StateStore → DBWrapper adapter

  • Adds SSPebbleDB (raw MVCC) and SSComposite (full CompositeStateStore with EVM sub-DB routing) so the same ERC20 changeset workload can benchmark the historical state store

  • Suppports mode for SC + SS

Testing performed to validate your change

  • running bench against various different configs

Add SSPebbleDB and SSComposite backend types so the existing ERC20
benchmark can drive the historical state store using the same changeset
write path.

Made-with: Cursor
@github-actions
Copy link

github-actions bot commented Feb 28, 2026

The latest Buf updates on your PR. Results from workflow Buf / buf (pull_request).

BuildFormatLintBreakingUpdated (UTC)
✅ passed✅ passed✅ passed✅ passedMar 2, 2026, 4:09 PM

Add a combinedWrapper that fans out changeset writes to both a State
Commit and State Store backend, mirroring production. Two new backend
types: FlatKV+SSPebble and CompositeDual+SSComposite.

Made-with: Cursor
@Kbhat1 Kbhat1 requested review from cody-littley and yzang2019 and removed request for yzang2019 February 28, 2026 19:15
Verifies SSPebbleDB and FlatKV+SSPebble work with the existing
runBenchmark harness (version tracking, changeset generation, etc).

Made-with: Cursor
SSPebbleDB bypassed the SS layer (Tier 2) and hit raw PebbleDB MVCC
directly - not a real production path. All SS backends now go through
CompositeStateStore, matching the architecture. Extracted shared
openSSComposite helper to deduplicate SS creation.

Made-with: Cursor
Drop FlatKV+SSComposite since the production path is CompositeDual+SS.
Fix combinedWrapper version tracking to use SS version (consistent
across all SC backends).

Made-with: Cursor
@Kbhat1 Kbhat1 changed the title Extend cryptosim DB benchmark to support state store (SS) backends Extend DB benchmark to support state store (SS) backends Feb 28, 2026
Copy link
Contributor

@cody-littley cody-littley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM once the config file is fixed.

I like how low-touch this ended up being... I was initially concerned that this would result in a big diff inside the benchmark that would conflict with my in-flight branches. So only seeing a new wrapper is a relief. 😅

@codecov
Copy link

codecov bot commented Mar 2, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 58.14%. Comparing base (b6685c1) to head (ef1dfe7).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #2995      +/-   ##
==========================================
- Coverage   58.30%   58.14%   -0.16%     
==========================================
  Files        2108     2113       +5     
  Lines      173688   173518     -170     
==========================================
- Hits       101275   100899     -376     
- Misses      63392    63596     +204     
- Partials     9021     9023       +2     
Flag Coverage Δ
sei-db 70.41% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 92 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants