Skip to content

chore: add block building benchmark test for public-compute-heavy txs#11991

Merged
dbanks12 merged 5 commits intomasterfrom
db/heavy-compute-blockbuilding-bench
Feb 14, 2025
Merged

chore: add block building benchmark test for public-compute-heavy txs#11991
dbanks12 merged 5 commits intomasterfrom
db/heavy-compute-blockbuilding-bench

Conversation

@dbanks12
Copy link
Copy Markdown
Contributor

@dbanks12 dbanks12 commented Feb 13, 2025

Add an alternative mode for blockbuilding benchmark test that spams public-compute-heavy transactions (a big sha256) instead of the tiny/simple transactions in the standard one.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Feb 13, 2025

Changes to public function bytecode sizes

Generated at commit: 2be2488359c23c28ea40a3ef218a4b3e4959f59a, compared to commit: be1b563ffe99689af45c9241a1d94d53de1c4e35

🧾 Summary (100% most significant diffs)

Program Bytecode size in bytes (+/-) %
Benchmarking::public_dispatch +4,822 ❌ +144.07%

Full diff report 👇
Program Bytecode size in bytes (+/-) %
Benchmarking::public_dispatch 8,169 (+4,822) +144.07%

@dbanks12 dbanks12 requested a review from just-mitch February 14, 2025 01:23
@dbanks12 dbanks12 enabled auto-merge (squash) February 14, 2025 17:42
@dbanks12 dbanks12 disabled auto-merge February 14, 2025 17:44
@dbanks12 dbanks12 merged commit 8c5e857 into master Feb 14, 2025
@dbanks12 dbanks12 deleted the db/heavy-compute-blockbuilding-bench branch February 14, 2025 17:44
// Does a bunch of heavy compute
#[public]
fn sha256_hash_2048(data: [u8; 2048]) -> [u8; 32] {
std::hash::sha256(data)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I guess this is ok if you want just any heavy compute, but looks like Tom has been migrating things: #11696 to another sha?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants