ChainSafe / ChainSafe/lodestar
Performance issue archiving DataColumnSidecars
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 483
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 150
Description
### Describe the bug
On one of lido nodes, archiving blocks could take up to 1.5 minutes
here is 1h interval
I think the spike mainly happened due to gc
### Expected behavior
as short as possible
### Steps to reproduce
_No response_
### Additional context
_No response_
### Operating system
Linux
### Lodestar version or commit hash
v1.38.0
Contributor guide
Research direction
No source file, test, or entry point is named. Start by locating the DataColumnSidecars archiving path in the Lodestar TypeScript code and measure block-archiving time and garbage-collection behavior on Linux; done means the reported up-to-1.5-minute spikes are reduced and the result is validated against v1.38.0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100