Investigate tokio runtime metrics

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

Maintainers usually reply within 1 day

@LesnyRumcajs is already working on this.

Since Oct 8, 2026.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
rust
Domain
observability

Research direction

Start with the linked Tokio performance article, then inspect Forest’s existing metrics and Tokio integration points. Determine which runtime measurements are useful and how they should be exported. Done means an agreed scope and implementation approach for Tokio runtime metrics.

Written by the indexing model from the issue text.

Description

Type: Task

Summary

Difficult to improve what you don't measure, and even though Forest uses async tokio extensively, we don't really export any metrics around it, making us blind to some, potentially, obvious inefficiencies.

I don't have a first-hand knowledge what's the best approach there, this is to be investigated.

Additional Links & Resources

https://dial9-rs.github.io/blog/principles-for-fast-tokio-applications/

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.