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,55 @@ 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.
Number of blocks between snapshots when db-sync is near the tip of the chain (within approximately 10 minutes). More frequent snapshots when following the tip ensure faster recovery from rollbacks.
630
+
631
+
### Lagging
632
+
633
+
`snapshot_interval.lagging`
634
+
635
+
* Type: `integer`
636
+
* Default: `100000`
637
+
638
+
Number of blocks between snapshots when db-sync is syncing and significantly behind the tip of the chain. Less frequent snapshots during initial sync improves performance by reducing expensive disk operations.
639
+
640
+
### Example
641
+
642
+
```json
643
+
{
644
+
"snapshot_interval": {
645
+
"following": 500,
646
+
"lagging": 100000
647
+
}
648
+
}
649
+
```
650
+
651
+
### Performance Considerations
652
+
653
+
-**Smaller `following` value**: Faster recovery from rollbacks when near the tip, but more frequent disk writes
654
+
-**Larger `lagging` value**: Faster initial sync with reduced IOPS, but slower recovery if rollback is needed during sync
655
+
-**Recommended for initial sync**: Use a large `lagging` value (50000-100000) to maximise sync speed
656
+
-**Recommended when near tip**: Use a small `following` value (500-1000) to enable quick rollback recovery
0 commit comments