Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(docs): add syncing duration explanation #2459

Merged
merged 2 commits into from
Nov 13, 2024
Merged

chore(docs): add syncing duration explanation #2459

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7b8762a
add syncing duration explanation
chmllr Nov 12, 2024
ce9c146
adds context on how to get bps
chmllr Nov 13, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions docs/content/operate/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,17 @@
- Note that setting up cosmovisor is strongly advised to support smooth network upgrades. See our [halovisor build scripts](https://github.com/omni-network/omni/tree/main/scripts/halovisor) for inspiration.
- Note that before starting geth, it must first be initialised with the relevant `execution-genesis.json` file via `geth init` (see [omega](https://github.com/omni-network/omni/tree/main/lib/netconf/omega) and [mainnet](https://github.com/omni-network/omni/tree/main/lib/netconf/mainnet)).

### How long does syncing take?

The time it takes for Geth to do a fullsync (snapsync is not supported yet) depends largely on your disk write throughput.
Syncing speed is directly proportional to write performance.
We observed the following numbers in practice:
- 200 MB/s disk write speed achieves approximately 40 blocks per second.
- 1.5 GB/s disk write speed achieves around 460 blocks per second.

To estimate your full sync time, check the current chain height (see [omniscan.network](https://omniscan.network)) and divide this number by your blocks-per-second rate to get a rough duration in seconds.
You can estimate your blocks-per-second rate by monitoring the Geth logs: the log line starting with `Imported new potential chain segment` contains the `number` parameter denoting the last imported block height.

### How to check if the validator is ready?
A node is considered ready when it is healthy and functions as intended.
This means both the consensus and execution chains are fully synchronized, there are execution and consensus P2P peers connected, and new blocks are being produced.
Expand Down
Loading