You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, checkpoint creation is triggered when more than 40 WAL files accumulate. Replaying each WAL file can take very roughly about 10-20 seconds each (depending on system specs, other activity, etc.)
Prior to PR #1944, it wasn't feasible to create checkpoints more frequently because checkpoint creation took 12-15+ hours on mainnet. After PR #1944, checkpoint creation should take very roughly around 15 minutes while consuming much less RAM.
EN startup time can be faster by having fewer WALs to replay during EN startup.
The Proposed Solution
Compare the benchmarks (checkpoint file loading + replaying WALS) using 40 WALs vs 20 WALs.
If needed, configure EN to use a different number of WALs to trigger checkpoint creation.
Preliminary Benchmarks
On benchnet, using loading checkpoint and replaying WALs takes about:
Problem
EN startup time can be improved.
Currently, checkpoint creation is triggered when more than 40 WAL files accumulate. Replaying each WAL file can take very roughly about 10-20 seconds each (depending on system specs, other activity, etc.)
Prior to PR #1944, it wasn't feasible to create checkpoints more frequently because checkpoint creation took 12-15+ hours on mainnet. After PR #1944, checkpoint creation should take very roughly around 15 minutes while consuming much less RAM.
EN startup time can be faster by having fewer WALs to replay during EN startup.
The Proposed Solution
Preliminary Benchmarks
On benchnet, using loading checkpoint and replaying WALs takes about:
Updates https://github.com/dapperlabs/flow-go/issues/6114
The text was updated successfully, but these errors were encountered: