Improve `eth_*` methods performance

Open
#7,008 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Quiet
Tech stack
go, rust

Research direction

Start by reviewing the attached real-traffic benchmark images and identifying the affected eth_* methods; the issue names no files or tests. Compare each method with Lotus, excluding debug_traceBlockByNumber and debug_traceTransaction. Done means every remaining listed method is at least as fast as Lotus.

Written by the indexing model from the issue text.

Description

Type: Epic

Summary

We've got some numbers on real traffic; for several methods they don't look good and while Forest takes significantly less resources, there should be some room for improvement.

Image Image

Motivation

Performance and resource usage are the selling points of Forest. There's nothing we can't do in Rust that is done in Golang.

Tasks

  • All listed methods should be at least as fast as in Lotus - few times slower is not acceptable
  • Ignore debug_traceBlockByNumber and debug_traceTransaction, they were not actually invoked

Risks & Dependencies

Additional Links & Resources

Dominant language
Rust
Stars
700
Forks
201
Avg merge
1d 17h
Merged PRs (30d)
65

Getting set up

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 ChainSafe/forest

All issues in ChainSafe/forest

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.