DaWe35 · November 6, 2024 19:13 · Feb 25, 2024 · Feb 25, 2024 · Feb 18, 2024 · Feb 18, 2024
diff --git a/monerod-sync.md b/monerod-sync.md
@@ -30,3 +30,16 @@ Prune blockchain
 | --fast-block-sync (default 1) | CPU usage | Sync up most of the way by using embedded, known block hashes.|
 | --prune-blockchain | Storage usage | Some unnecessary data won't be stored on your computer, reducing the local blockchain database size by ~66%|
 | --sync-pruned-blocks | Bandwidth | Allow syncing from nodes with only pruned blocks (only when --prune-blockchain	is on) |
+
+## Sync time estimates
+
+All estimates are calculated on 2024 february. I ran tests in docker on a 3 vCore, 4GB RAM, 200 Mbit/s port, SSD VPS.
+At this date, the uncompressed Monero block chain is size was 180GB. You can get the current number by running this command: 
+
+`x=$(curl -sd '{"jsonrpc":"2.0","id":"0","method":"get_info"}' http://node.moneroworld.com:18089/json_rpc | grep 'database_size' |  sed -r 's/.*: ([0-9]*)\,.*/\1/g'); y=$((x/1024/1024/1024)); echo -e "\tCurrent uncompressed Monero block chain is: "$y"GB"`
+
+- Full sync: monerod estimates a 15 days. I'll update this when I get more precise info, I started the sync around 2024-02-25 13:00 UTC
+- Fast sync takes around 4 days to complete
+- Pruned sync should be just a bit faster than fast sync when `--sync-pruned-blocks` is on. Don't expect big performance improvements.
+
+Please comment your tests so we can see a better average.
diff --git a/monerod-sync.md b/monerod-sync.md
@@ -4,7 +4,7 @@
 
 Download, verify, and store the whole blockchain
 
-`monerod --fast-block-sync 0`
+`monerod --fast-block-sync=0`
 
 ### Fast sync
 

diff --git a/monerod-sync.md b/monerod-sync.md
@@ -29,4 +29,4 @@ Prune blockchain
 |--|--|--|
 | --fast-block-sync (default 1) | CPU usage | Sync up most of the way by using embedded, known block hashes.|
 | --prune-blockchain | Storage usage | Some unnecessary data won't be stored on your computer, reducing the local blockchain database size by ~66%|
-| --sync-pruned-blocks | Bandwidth | Allow syncing from nodes with only pruned blocks |
+| --sync-pruned-blocks | Bandwidth | Allow syncing from nodes with only pruned blocks (only when --prune-blockchain	is on) |
diff --git a/monerod-sync.md b/monerod-sync.md
@@ -1,4 +1,4 @@
-## Modes
+## Sync modes
 
 ### Full node
 

diff --git a/monerod-sync.md b/monerod-sync.md
@@ -1,3 +1,5 @@
+## Modes
+
 ### Full node
 
 Download, verify, and store the whole blockchain

diff --git a/monerod-sync.md b/monerod-sync.md
@@ -0,0 +1,30 @@
+### Full node
+
+Download, verify, and store the whole blockchain
+
+`monerod --fast-block-sync 0`
+
+### Fast sync
+
+Sync up most of the way by using embedded, known block hashes.
+
+`monerod`
+
+*As you can see, fast block sync is on by default.*
+
+### Prune
+
+Prune blockchain
+
+`monerod --prune-blockchain --sync-pruned-blocks`
+
+*Again, fast-block-sync is on by default in this case too.*
+
+
+## Explanation
+
+|Flag|Reduces|Explanation|
+|--|--|--|
+| --fast-block-sync (default 1) | CPU usage | Sync up most of the way by using embedded, known block hashes.|
+| --prune-blockchain | Storage usage | Some unnecessary data won't be stored on your computer, reducing the local blockchain database size by ~66%|
+| --sync-pruned-blocks | Bandwidth | Allow syncing from nodes with only pruned blocks |