Open keithchew opened 4 days ago
hi, can you try branch new-payload2
and see if the issue persists
hi @Giulio2002, tried new-payload2 branch, behavior is the same as v2.60.2. CPU constantly hits and stays at 100% ceiling... v2.60.1 is more periodic and less aggressive...
v2.60.1
v2.60.2/new-payloads
In this setup, erigon is running on ubuntu as guest OS under hyper-v as host. Still a regression though...
could you try commit e8c5632b0b14a87072924334c6359dd6fbcf57ba and 478b5b2ed969cc5daef1d7dcca00d0a19bccabe9? If you could do, it would really help me, i am currently resyncing a sepolia node to reproduce
I have applied both commits to v2.60.1, and CPU did not spike. Let me know if you would like me to try any other commits to help track this down.
try 2e590ce9677cbadd5b7d1b4d8370af89aed9c7f8, aa591fd0aeaa34529fe3963f46d7e4a7701cf10e, c637e37e63b5606d489b7602b412289191f9b8a5 and cac1c2d135f675ca456e543f81900f89515dac50 . My sepolia node is still syncing, I would really appreciate if you could attempt these
Just upgraded from v2.60.1 to v2.60.2, running on sepolia.
After upgrade, disk usage spikes to 100%. Reverting back to v2.60.1, disk usage is goes back down to under 10%.
Note that after reverting, erigon downloads the snapshots (which disk usage is 100%) but after that, it goes back to normal.
Also observed that in v2.60.1, logs for new payload is as below:
But in v2.60.2:
Looks like a logic change in v2.60.2 is triggering the EngineBlockDownloader into action, but not in v2.60.1?