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
@@ -602,3 +603,43 @@ Stops db-sync after processing the specified block number. Useful for testing an
602
603
}
603
604
```
604
605
606
+
## Snapshot Interval
607
+
608
+
`snapshot_interval`
609
+
610
+
* Type: `object`
611
+
* Optional: When not specified, uses default values
612
+
613
+
Controls how frequently ledger state snapshots are taken during sync. Taking snapshots less frequently during initial sync can significantly improve sync performance by reducing IOPS and disk throughput consumption.
Epoch threshold used to determine snapshot behavior. When syncing reaches this epoch or later, db-sync is considered to be approaching or at the current tip of the chain. Combined with time-based detection (within 10 days of current time), this ensures snapshots are taken every epoch when near the tip for fast rollback recovery. During earlier epochs or when syncing behind, snapshots are taken every 10 epochs.
629
+
630
+
### Example
631
+
632
+
```json
633
+
{
634
+
"snapshot_interval": {
635
+
"near_tip_epoch": 580
636
+
}
637
+
}
638
+
```
639
+
640
+
### Performance Considerations
641
+
642
+
-**Lower `near_tip_epoch` value**: Start taking frequent epoch-based snapshots earlier in the chain history
643
+
-**Higher `near_tip_epoch` value**: Delay frequent snapshots until later in the chain, improving sync speed for longer. During initial sync (before reaching `near_tip_epoch`), snapshots are taken every 10 epochs
644
+
-**Near tip detection**: Automatically switches to epoch-based snapshots when within 10 days of current time, regardless of epoch number
0 commit comments