What did you expect to see?
I expected the observer to process/validate blocks fast enough to at least keep up with the chain head on our devnet. Since new blocks started to produce roughly every ~2 seconds by heartbeat mechanics, the observer should have a sustained processing rate ≥ block production rate (ideally higher during initial catch-up), so that the sync lag shrinks over time instead of growing.
What did you see instead?
On our devnet, the observer’s block validation results in an extremely long initial sync because the chain already has 250k+ blocks and new blocks are produced every ~2 seconds. Previously, when the devnet produced roughly one block every ~10 seconds, the observer was able to keep up and syncing was not an issue.
With the current rate (~0.3 blocks/sec), the observer cannot catch up and will fall further behind cumulatively, leading to an ever-increasing delay between the observer and the blockchain head. At this rate, syncing 250k blocks takes ~234 hours (~9.7 days)
What did you expect to see?
I expected the observer to process/validate blocks fast enough to at least keep up with the chain head on our devnet. Since new blocks started to produce roughly every ~2 seconds by heartbeat mechanics, the observer should have a sustained processing rate ≥ block production rate (ideally higher during initial catch-up), so that the sync lag shrinks over time instead of growing.
What did you see instead?
On our devnet, the observer’s block validation results in an extremely long initial sync because the chain already has 250k+ blocks and new blocks are produced every ~2 seconds. Previously, when the devnet produced roughly one block every ~10 seconds, the observer was able to keep up and syncing was not an issue.
With the current rate (~0.3 blocks/sec), the observer cannot catch up and will fall further behind cumulatively, leading to an ever-increasing delay between the observer and the blockchain head. At this rate, syncing 250k blocks takes ~234 hours (~9.7 days)