Progress:
Code:
Day 1:
spiker777
Day 2:
apogio
oktana
Day 5:
tech30338
Ultegra134
DYING_S0UL
spiker777
Day 2:
apogio
oktana
Day 5:
tech30338
Ultegra134
DYING_S0UL
Topic: 🍑 PeachBitcoin [CHALLENGE] Run A Bitcoin Node: 14 Days To 14 Merits - page 151. (Read 36675 times)
January 09, 2024, 03:20:36 AM
I was busy yesterday and forgot to post the progress. Apologies!
Progress:
Progress:
January 09, 2024, 02:36:25 AM
Day 5
Code:
{
"chain": "main",
"blocks": 824969,
"headers": 824969,
"bestblockhash": "000000000000000000037c59e3d40eddc1d97d53494f5fb735abf3cacab4a165",
"difficulty": 73197634206448.34,
"time": 1704785372,
"mediantime": 1704783139,
"verificationprogress": 0.9999988824061389,
"initialblockdownload": false,
"chainwork": "000000000000000000000000000000000000000064be9d7a17228c188f70ff1a",
"size_on_disk": 4902415622,
"pruned": true,
"pruneheight": 822506,
"automatic_pruning": true,
"prune_target_size": 4999610368,
"warnings": ""
}
"chain": "main",
"blocks": 824969,
"headers": 824969,
"bestblockhash": "000000000000000000037c59e3d40eddc1d97d53494f5fb735abf3cacab4a165",
"difficulty": 73197634206448.34,
"time": 1704785372,
"mediantime": 1704783139,
"verificationprogress": 0.9999988824061389,
"initialblockdownload": false,
"chainwork": "000000000000000000000000000000000000000064be9d7a17228c188f70ff1a",
"size_on_disk": 4902415622,
"pruned": true,
"pruneheight": 822506,
"automatic_pruning": true,
"prune_target_size": 4999610368,
"warnings": ""
}
January 09, 2024, 02:08:29 AM
DAY 2:
Quote
{
"chain": "main",
"blocks": 824966,
"headers": 824966,
"bestblockhash": "000000000000000000004f3a85a15a4a66d8d25c719e2eb6fcbc282365b38f6e",
"difficulty": 73197634206448.34,
"time": 1704783575,
"mediantime": 1704782509,
"verificationprogress": 0.9999969936535228,
"initialblockdownload": false,
"chainwork": "000000000000000000000000000000000000000064bdd5c15a751e9a19088eef",
"size_on_disk": 612971397864,
"pruned": false,
"warnings": ""
}
"chain": "main",
"blocks": 824966,
"headers": 824966,
"bestblockhash": "000000000000000000004f3a85a15a4a66d8d25c719e2eb6fcbc282365b38f6e",
"difficulty": 73197634206448.34,
"time": 1704783575,
"mediantime": 1704782509,
"verificationprogress": 0.9999969936535228,
"initialblockdownload": false,
"chainwork": "000000000000000000000000000000000000000064bdd5c15a751e9a19088eef",
"size_on_disk": 612971397864,
"pruned": false,
"warnings": ""
}
January 08, 2024, 04:20:54 PM
DAY 5 progress:
January 08, 2024, 03:02:57 PM
Day 5:
Half way through, 4 years and 18 weeks behind. We're getting closer.
Quote
{
"chain": "main",
"blocks": 592868,
"headers": 824904,
"bestblockhash": "0000000000000000000ec5096aadf8f69d16109bc0bf7df8d388fb79ee3715a3",
"difficulty": 10771996663680.4,
"time": 1567407779,
"mediantime": 1567404528,
"verificationprogress": 0.4960159278174696,
"initialblockdownload": true,
"chainwork": "000000000000000000000000000000000000000008310a5325954201c052c0c7",
"size_on_disk": 32080535585,
"pruned": true,
"pruneheight": 568134,
"automatic_pruning": true,
"prune_target_size": 34999369728,
"warnings": ""
}
"chain": "main",
"blocks": 592868,
"headers": 824904,
"bestblockhash": "0000000000000000000ec5096aadf8f69d16109bc0bf7df8d388fb79ee3715a3",
"difficulty": 10771996663680.4,
"time": 1567407779,
"mediantime": 1567404528,
"verificationprogress": 0.4960159278174696,
"initialblockdownload": true,
"chainwork": "000000000000000000000000000000000000000008310a5325954201c052c0c7",
"size_on_disk": 32080535585,
"pruned": true,
"pruneheight": 568134,
"automatic_pruning": true,
"prune_target_size": 34999369728,
"warnings": ""
}
Half way through, 4 years and 18 weeks behind. We're getting closer.
January 08, 2024, 01:13:16 PM
Great Initiative @NotATether I always wanted to try Bitcoin Core but heard that it'll consume a lot of Data so I was kinda of confused. but now to take part in your challenge I am going to have a Experience Bitcoin Core Too And hopefully learn something new as well.
Day 1 For Me:
It is my first time with Bitcoin Core in fact with any nodes. so Please guide me if I am doing it wrong.
Day 1 For Me:
It is my first time with Bitcoin Core in fact with any nodes. so Please guide me if I am doing it wrong.
January 08, 2024, 09:54:12 AM
The workload is equivalent to downloading a 600GB file in your browser and scanning it for viruses.
It's a lot more than that. My (laptop) sync is almost done, and my disk %util is now consistently around 96%. It has written 4.58 TB to disk in 42 hours.When it's done, I'll create a progress graph.
The total size of the chainstate will only be ~9 GB once all is said and done, but it is updated after every block to remove all spent UTXOs and update all newly created UTXOs. Ideally this would be stored entirely within your RAM and only flushed to disk when you shutdown your node, but few people are running Core with a big enough dbcache, and so the chainstate file on your SSD is constantly being updated, especially during the IBD. Once you are fully synced and running, then Core will cache as much of the chainstate as possible in your RAM (up to your dbcache limit), and will optimize what it can cache to RAM (i.e. will preferentially cache newer UTXOs which are more likely to be spent rather than ones which have been dormant for years, specifically to minimize how much needs to be written to the chainstate file).
The more RAM you allocate, the less your chainstate will be written to. The less often you shutdown your node, the less your chainstate will be written to.
January 08, 2024, 07:55:37 AM
It's specified in megabytes and it can be a maximum of 16GB.
Actually it's specified in mebibytes, according to this from bitcoin's github:
Quote
-dbcache= - the UTXO database cache size, this defaults to 450. The unit is MiB (1024).
The minimum value for -dbcache is 4.
The minimum value for -dbcache is 4.
It doesn't really make a big difference, I just mention it for the sake of accuracy.
Well, yeah. Megabytes is technically 1000 Kilobytes, but the only people who use that measurement are disk & memory manufacturers, everyone else considers them a factor of 1024 although technically it is not.
January 08, 2024, 06:53:24 AM
It's specified in megabytes and it can be a maximum of 16GB.
Actually it's specified in mebibytes, according to this from bitcoin's github:
Quote
-dbcache= - the UTXO database cache size, this defaults to 450. The unit is MiB (1024).
The minimum value for -dbcache is 4.
The minimum value for -dbcache is 4.
It doesn't really make a big difference, I just mention it for the sake of accuracy.
January 08, 2024, 06:33:52 AM
The workload is equivalent to downloading a 600GB file in your browser and scanning it for viruses.
It's a lot more than that. My (laptop) sync is almost done, and my disk %util is now consistently around 96%. It has written 4.58 TB to disk in 42 hours.When it's done, I'll create a progress graph.
Quote
the process of syncing your Core Node one time doesn't affect your disk life much if at all.
For a modern disk, that's correct. My 2 TB Samsung has 1200 TBW.One of my old SSDs can only write 36 TB. It won't instantly kill it, but it takes a significant chunk out of it's life.
January 08, 2024, 06:31:16 AM
With this speed, it is quick enough but I want to learn
How to set dbcache?
How to know how the sync progress kills % of my disk life?
How to set dbcache?
How to know how the sync progress kills % of my disk life?
Use the -dbcache setting in the command line or add dbcache=the value to your bitcoin.conf file. It's specified in megabytes and it can be a maximum of 16GB. Although most people should use 2 or 4GB of dbcache. There is little benefit to make it higher.
Are you using an HDD or SSD?
HDDs are designed to handle petabytes or at the very least, many, many terabytes of read/write IO total bytes. SSDs a bit less than that, but regardless, the process of syncing your Core Node one time doesn't affect your disk life much if at all. Having said that, if your disk is failing SMART tests, do not use any disk-intensive apps like running a Node, and get it replaced.
January 08, 2024, 06:22:44 AM
Yes, everyone can join. No, it will not kill your disk. The workload is equivalent to downloading a 600GB file in your browser and scanning it for viruses. Will that break your disk? No. No matter whether it is an HDD or SSD.
With this speed, it is quick enough but I want to learnHow to set dbcache?
How to know how the sync progress kills % of my disk life?
I have Core i7, 8GB RAM and think I won't to do anything with dbcache, want to know only.
January 08, 2024, 06:21:19 AM
Yes, everyone can join. No, it will not kill your disk. The workload is equivalent to downloading a 600GB file in your browser and scanning it for viruses. Will that break your disk? No. No matter whether it is an HDD or SSD.
January 08, 2024, 06:11:29 AM
Can I join it?
I actually run a prune node since 3 Jan but on my desktop because I have my laptop to repair something for a few days. The syncing on desktop is very low.
Today, I copied the prune node data to my laptop, and it syncs very quickly.
Reading LoyceV's posts, I am worrying that it will kill my laptop and its disk. Should I continue?
I actually run a prune node since 3 Jan but on my desktop because I have my laptop to repair something for a few days. The syncing on desktop is very low.
Today, I copied the prune node data to my laptop, and it syncs very quickly.
Code:
{
"chain": "main",
"blocks": 420024,
"headers": 824850,
"bestblockhash": "00000000000000000165e59d1ba94b2b386a4d80aa318077941ac020c979e432",
"difficulty": 213398925331.3239,
"time": 1468095911,
"mediantime": 1468095039,
"verificationprogress": 0.1489870150749924,
"initialblockdownload": true,
"chainwork": "0000000000000000000000000000000000000000001f2d93b0bc10f3ee0455d7",
"size_on_disk": 3332447503,
"pruned": true,
"pruneheight": 416588,
"automatic_pruning": true,
"prune_target_size": 4999610368,
"warnings": ""
}
Reading LoyceV's posts, I am worrying that it will kill my laptop and its disk. Should I continue?
January 08, 2024, 04:17:03 AM
Great initiative NotATether.
I am obviously running nodes since I started my bitcoin journey, but since I have less than 1000 merits, I will participate with one of my nodes.
DAY 1:
I am obviously running nodes since I started my bitcoin journey, but since I have less than 1000 merits, I will participate with one of my nodes.
DAY 1:
Code:
{
"chain": "main",
"blocks": 824839,
"headers": 824839,
"bestblockhash": "00000000000000000000e205f4449a5ddbbe5aa29964d00b05c6b88e4ad3757c",
"difficulty": 73197634206448.34,
"time": 1704704580,
"mediantime": 1704699308,
"verificationprogress": 0.9999952006027929,
"initialblockdownload": false,
"chainwork": "0000000000000000000000000000000000000000649ccedf7c72035b2f18ad28",
"size_on_disk": 612733635152,
"pruned": false,
"warnings": ""
}
January 08, 2024, 04:07:18 AM
Another experiment:
I'll keep hourly status-snapshots again.
I'm running this on a 6-core Xeon (E-2236) with 32 GB RAM and 1 GBit internet (and HDD, but I won't be using that).
This took 11 hours and 10 minutes to sync Code:
./bitcoind -dbcache=4096 -prune=550 -datadir=/dev/shm/bitcoin
I'm running this on a 6-core Xeon (E-2236) with 32 GB RAM and 1 GBit internet (and HDD, but I won't be using that).
Unfortunately, I didn't store data from getblockchaininfo. Somehow bitcoin-cli couldn't connect to the daemon now. So I can't tell how the progress estimate changed over time. January 08, 2024, 02:41:02 AM
Day 4
Code:
{
"chain": "main",
"blocks": 824835,
"headers": 824835,
"bestblockhash": "00000000000000000003d06c35c82f095a9f411d21fb53ebda255fb46be0a1ad",
"difficulty": 73197634206448.34,
"time": 1704699350,
"mediantime": 1704698646,
"verificationprogress": 0.9999996401959509,
"initialblockdownload": false,
"chainwork": "0000000000000000000000000000000000000000649bc493d635715d3be2c244",
"size_on_disk": 4957545000,
"pruned": true,
"pruneheight": 822352,
"automatic_pruning": true,
"prune_target_size": 4999610368,
"warnings": ""
}
January 07, 2024, 06:16:28 PM
I'm in! I started about 4 hours ago and this is my progress. The time left is showing just 3 days but it’s not always so, sometimes it reset and goes back to an average of 12 days or so.
These are my settings. I set pruning to 20GB (I think it should be more because my external ssd drive which I am using has over 500GB of space).
These are my settings. I set pruning to 20GB (I think it should be more because my external ssd drive which I am using has over 500GB of space).
January 07, 2024, 01:41:35 PM
Which SSD do you use and what is its TBW?
It's an older 128 GB disk, with 70 TBW. It's not something I worry about now, since that disk has served me for many years and still has enough left, but I was surprised that just 1 blockchain download will now take 10-20% of it's "life". It has written another 0.3 TB since my previous post.Another experiment:
Code:
./bitcoind -dbcache=4096 -prune=550 -datadir=/dev/shm/bitcoin
I'm running this on a 6-core Xeon (E-2236) with 32 GB RAM and 1 GBit internet (and HDD, but I won't be using that).
I expect this one not to slow down when chainstate grows, because it won't be low on memory (and even though dbcache isn't that high, that doesn't matter when using a RAM-drive for storage).
January 07, 2024, 12:50:02 PM
I checked something else: writing 20-50 MB/s for a few days is very destructive for an SSD! Until now, I've written 2.6 TB in less than a day, which is already more than 10% of all writes that SSD has seen in it's entire life! My current estimate for this old disk is that this is going to cost 10-20% of the SSD's TBW (TeraBytes Written, a design-life span for SSDs). This is destructive for old SSDs with little RAM!
Which SSD do you use and what is its TBW?
Now that you made me curious about the wear of my own SSD in my Umbrel node (mine is a Samsung SSD 860 Evo 1TB), I checked S.M.A.R.T. attributes:
Code:
=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
9 Power_On_Hours 0x0032 094 094 000 Old_age Always - 25807
12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 787
177 Wear_Leveling_Count 0x0013 087 087 000 Pre-fail Always - 184
179 Used_Rsvd_Blk_Cnt_Tot 0x0013 100 100 010 Pre-fail Always - 0
181 Program_Fail_Cnt_Total 0x0032 100 100 010 Old_age Always - 0
182 Erase_Fail_Count_Total 0x0032 100 100 010 Old_age Always - 0
183 Runtime_Bad_Block 0x0013 100 100 010 Pre-fail Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0032 059 047 000 Old_age Always - 41
195 Hardware_ECC_Recovered 0x001a 200 200 000 Old_age Always - 0
199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0
235 Unknown_Attribute 0x0012 099 099 000 Old_age Always - 41
241 Total_LBAs_Written 0x0032 099 099 000 Old_age Always - 202678239705
This SSD has endured two full intial blockchain downloads and 24/7 operation as Umbrel node for about two years now. Total Power_On_Hours indicates almost three years of use but the first year of life was not as storage device for a Bitcoin node.
Attribute ID# 177 Wear_Leveling_Count is to be read as remaining percentage of endurance. So after something over a total of 94TiBW (1TiB is 240 bytes) my SSD is at 87% of remaining endurance. I'm not worried at all now. I was a bit worried when I read LoyceV's post.
I hope this is not off-topic here.
Jump to: