Skip to content

Commit d9d4dc2

Browse files
committed
Merge #1011: stats: update datadir_gb & pruned_gb
b2fccc1 stats: update pruned_gb to 10GB (fanquake) 9b02588 stats: update datadir_gb to 600GB (fanquake) Pull request description: Should close #1010. ACKs for top commit: glozow: Matches https://github.com/bitcoin/bitcoin/blob/6dabb315c4fb2cdc4421ed34dee5e19042f899c3/src/kernel/chainparams.cpp#L121-L122, so ACK b2fccc1 Tree-SHA512: 81bb573e1bd1ee4a2fa119cc6b6d060e57b4c81419541ce66693a45ef330010e437d3423b7f77fa4db81e5ef956a0d5c9a554f9bb6aaa7981d65e4f760f63e3b
2 parents 47748c1 + b2fccc1 commit d9d4dc2

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

_data/stats.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
## Size of the Bitcoin Core data directory running with default settings.
22
## Suggest rounding up by about 10% so it doesn't need to be updated
33
## too often.
4-
datadir_gb: "500"
4+
datadir_gb: "600"
55

66
## Size of the datadir with the maximum allowed pruning enabled.
77
## Suggest rounding up a little bit to give room for growth in the UTXO
88
## set and to account for things like pruning only happening
99
## at blk file boundaries and mempool saving.
10-
pruned_gb: "6"
10+
pruned_gb: "10"
1111

12-
## Size of monthly increase in dadadir size. For 1 MB blocks, 144
12+
## Size of monthly increase in datadir size. For 1 MB blocks, 144
1313
## blocks per day, 30 days per month, 1000 MB/GB: 1*144*30/1000 = 4.32 GB.
1414
## Rounding that up to 5 GB and assuming it could quickly double with
1515
## increased segwit adoption gives a range of 5 to 10 GB/month.

0 commit comments

Comments
 (0)