ChainSafe / ChainSafe/lodestar

[fulu] Inefficient network processor in fusaka-devnet-3

Open
#8,270 0 comments 0 reactions 0 assignees View on GitHub
meta-bug spec-fulu :zebra:
Dominant language
TypeScript
Stars
1.4k
Forks
483
Avg merge
1d 16h
Merged PRs (30d)
150

Description

### Describe the bug

network processor "cannot accept work" is high in `fusaka-devnet-3` super nodes

Image

this is on a 1k hoodi node (which does not subscribe to all subnets)

Image

"regen busy" is the main reason

Image

this could lead to higher wait time of jobs, especially `beacon_attestation`, it could be ~1.7s

Image

### Expected behavior

"cannot accept work" should be close to 0, or need to investigate the reason if not

### Steps to reproduce

_No response_

### Additional context

_No response_

### Operating system

Linux

### Lodestar version or commit hash

unstable

Contributor guide

Open the contributing guide

Research direction

Start by locating the network processor and the metrics behind "cannot accept work" and "regen busy" in the Lodestar codebase. Reproduce or inspect this behavior on a fusaka-devnet-3 1k Hoodi node, then determine why work is rejected and verify that beacon_attestation wait time and rejected-work metrics improve.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.