gas benchmarks: Msize big sizes

Open
#5,347 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
blockchain, performance

Research direction

Start by running the gas compute benchmarks for msize values around 100k and 1M and compare ethrex's results with the reference benchmarks. Trace the execution path responsible for msize handling and identify the source of the 30% to 2x slowdown; done means the large-size benchmarks no longer show that gap.

Written by the indexing model from the issue text.

Description

performance

We're ok for msize compute benchmarks unless the memsize is big (e.g. 100k or 1M). In those cases we're from 30% to 2x behind.

Dominant language
Rust
Stars
897
Forks
229
Avg merge
1d 5h
Merged PRs (30d)
44

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lambdaclass/ethrex

All issues in lambdaclass/ethrex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.