Author

Topic: [CHALLENGE] Run A Bitcoin Node: 14 Days To 14 Merits - page 130. (Read 31466 times)

hero member
Activity: 770
Merit: 482
The possible reason for boosting the progress is, that when we restart the Bitcoin Core, It shuts down without updating the number of blocks left. But, once we start the Bitcoin core again, it synchronizes the downloaded blocks first and then starts downloading the next blocks and the number of blocks left gets frozen again or updated very slowly. I assume it happens due to the low RAM or CPU power.

Did you guys notice what I have posted and did you try to check if it's the same for you? My progress is getting slower day by day. For some unknown reason, I found out that my laptop was shut down in the morning but I kept it open. It happened two days in a row now. When I start it again, Seems like it was opened from sleep mode even though the sleep mode is disabled. I am not sure what is going on. My current progress is 61.77% on 5th day.

Day 5

hero member
Activity: 1470
Merit: 555
dont be greedy
Can I join the list? Here's my progress after 1 hour and 30 minutes. The stats show a pretty accurate increase per hour, starting at 0.5%, and now it's up to 3%, making me feel like things are picking up speed.

Starting to be interested in installing Bitcoin core (again) , because previously I failed to install Bitcoin core because it required a lot of data and time. Seem many people are just starting out now, I don't think it's too late to install this on my PC.

Day 1

sr. member
Activity: 1680
Merit: 288
Eloncoin.org - Mars, here we come!
Guys always make sure that you close your node properly or you could run into issues where it will start “Replaying blocks” and you’ll see a whole lot of “Rolling Forward” files in your debug. This can go on for hours (depending on how much cache that wasn’t flushed to your disk yet). Check this issue on GitHub

DAY 6
Code:
{
  "chain": "main",
  "blocks": 492565,
  "headers": 825750,
  "bestblockhash": "000000000000000000355b4701129a311ea26a2031a4bda1ae33cfab6b206002",
  "difficulty": 1452839779145.919,
  "time": 1509504213,
  "mediantime": 1509498223,
  "verificationprogress": 0.2807833463700093,
  "initialblockdownload": true,
  "chainwork": "000000000000000000000000000000000000000000a79f3d2b7ebd71520ad75a",
  "size_on_disk": 130402407155,
  "pruned": true,
  "pruneheight": 330303,
  "automatic_pruning": true,
  "prune_target_size": 399999238144,
  "warnings": ""
}
hero member
Activity: 560
Merit: 1060
DAY 7:

Code:
{
  "chain": "main",
  "blocks": 825744,
  "headers": 825744,
  "bestblockhash": "0000000000000000000058f2d949be5b6d75e4bdadc63b7e4d237653c55a436b",
  "difficulty": 73197634206448.34,
  "time": 1705221913,
  "mediantime": 1705217709,
  "verificationprogress": 0.9999968387607164,
  "initialblockdownload": false,
  "chainwork": "00000000000000000000000000000000000000006588283b277a0a0b617f8529",
  "size_on_disk": 614468712878,
  "pruned": false,
  "warnings": ""
}
member
Activity: 97
Merit: 43
Day 7

Code:
{
  "chain": "main",
  "blocks": 825181,
  "headers": 825739,
  "bestblockhash": "00000000000000000001a79d1975ec91e1b56d917ba0b7d512d85f7ba2987b9c",
  "difficulty": 73197634206448.34,
  "time": 1704917250,
  "mediantime": 1704914960,
  "verificationprogress": 0.998251616877296,
  "initialblockdownload": true,
  "chainwork": "000000000000000000000000000000000000000064f5bf2381acc5abe99aa04e",
  "size_on_disk": 4588482660,
  "pruned": true,
  "pruneheight": 823349,
  "automatic_pruning": true,
  "prune_target_size": 4999610368,
  "warnings": ""
}
full member
Activity: 728
Merit: 151
Defend Bitcoin and its PoW: bitcoincleanup.com
Day 10

Code:
{
  "chain": "main",
  "blocks": 825735,
  "headers": 825735,
  "bestblockhash": "000000000000000000001c49961b120924f5d9fbdb1133e024dcb0d45d86be20",
  "difficulty": 73197634206448.34,
  "time": 1705213523,
  "mediantime": 1705206428,
  "verificationprogress": 0.9999977432784773,
  "initialblockdownload": false,
  "chainwork": "00000000000000000000000000000000000000006585d110f171c18ffe4634a8",
  "size_on_disk": 4864753983,
  "pruned": true,
  "pruneheight": 823264,
  "automatic_pruning": true,
  "prune_target_size": 4999610368,
  "warnings": ""
}
sr. member
Activity: 1680
Merit: 288
Eloncoin.org - Mars, here we come!
Sometimes it makes noticeable difference, if it didn’t, I wouldn’t even do it more than once after first try.
Not just noticeable but highly noticeable. There was a time when I had 7.00% progress per hour after restarting Bitcoin core. I was shocked because my average progress was 0.50% per hour. I was wondering WTF just happended. After a minute or two, it went below 1% per hour. Lol  Tongue.


I think I’ve seen this one you’re narrating. I think it’s a different case entirely for me. I’m using an external drive that could get disconnected mistakenly, it happens when the hard drive gets suddenly disconnected and then I run Bitcoin Core again. I notice that if I was at 22% progress, it’ll start from 20% and will have a really high hourly progress, which I think is because it’s trying to verify the files again as it was untimely disconnected. Once it gets to where it was supposed to be, it drops the speed to the average you’ve been getting.
sr. member
Activity: 322
Merit: 318
The Alliance Of Bitcointalk Translators - ENG>BAN
Sometimes it makes noticeable difference, if it didn’t, I wouldn’t even do it more than once after first try.
Not just noticeable but highly noticeable. There was a time when I had 7.00% progress per hour after restarting Bitcoin core. I was shocked because my average progress was 0.50% per hour. I was wondering WTF just happended. After a minute or two, it went below 1% per hour. Lol  Tongue.



DAY 10 progress:

sr. member
Activity: 1680
Merit: 288
Eloncoin.org - Mars, here we come!
Mmm. But when I do this, I normally see little changes though. And it’s tempting to do when I see progress increase of 0.02 per hour.
Does it actually make any noticeable difference to the overall percentage though? I suspect what is happening is that when you restart you are simply interrupting the sampling process, and so when you restart Core thinks it is running faster than it is.

Sometimes it makes noticeable difference, if it didn’t, I wouldn’t even do it more than once after first try. It could be at 0.02% increase per hour but if I restart it, it could rise up to about 0.50% increase per hour. So it always feels like it’s stuck and just needs help. I sometimes take a screenshot so I can monitor if there’s progress. And most times, it really is stuck until you restart Bitcoin Core.

But logically, what Loyce said would be true because restarting it reloads everything and that sounds like extra work to what is supposedly running.
sr. member
Activity: 1007
Merit: 279
Payment Gateway Allows Recurring Payments
Day 6:

Code:
{
  "chain": "main",
  "blocks": 370317,
  "headers": 825665,
  "bestblockhash": "0000000000000000129bde658557c03015f4d0a6b9f290fe9cb46382b3265064",
  "difficulty": 52699842409.34701,
  "time": 1439850758,
  "mediantime": 1439848584,
  "verificationprogress": 0.08432399889509086,
  "initialblockdownload": true,
  "chainwork": "00000000000000000000000000000000000000000009592827025c22a0819ea0",
  "size_on_disk": 49146497620,
  "pruned": true,
  "pruneheight": 0,
  "automatic_pruning": true,
  "prune_target_size": 299999690752,
  "warnings": ""
}



Edit: just checked rame usage in task manager, Bitcoin Core using only 500 MB. while Google Chrome using a whooping 2 GB ram. lol
Chrome is an awful browser for many reasons, and resource usage is one of them.

In Bitcoin Core, go to Settings -> Options and check the size of the database cache you have set. Increase this if you want Core to use more RAM (you'll need to restart Core after you change this setting).
Just changed my cache to 2 GB lets see if the progress will improve. sorry I missed your post before.

hero member
Activity: 1680
Merit: 845
Day 10:
Quote

{
  "chain": "main",
  "blocks": 788918,
  "headers": 825653,
  "bestblockhash": "00000000000000000003e3aebd73c27bb3da00e64a34a4755189442d3e97d0c5",
  "difficulty": 48005534313578.78,
  "time": 1683622397,
  "mediantime": 1683620069,
  "verificationprogress": 0.9134302543868694,
  "initialblockdownload": true,
  "chainwork": "000000000000000000000000000000000000000047ef235959686b5c46d7e672",
  "size_on_disk": 31632268059,
  "pruned": true,
  "pruneheight": 773745,
  "automatic_pruning": true,
  "prune_target_size": 34999369728,
  "warnings": ""
}
I almost finished synchronizing. Currently at 91.5% and 34 weeks behind. It'll probably be fully synchronized in the upcoming 5 to 6 hours at most. I might consider increasing the prune block storage to 40 or 50 GB from 35, as we have a couple of days more till the end of the challenge. I wish I could download more, but my internet speed sucks big time.
hero member
Activity: 770
Merit: 482
it’s tempting to do when I see progress increase of 0.02 per hour.
I can't think of any reason why shutting down and restarting would improve things.


I guess, I know why and when it happens.
This is what noticed during the block download. When my Bitcoin core downloads the blocks, the main interface that shows the Number of blocks left: gets frozen for a few minutes. When it starts updating the number of blocks again, the download speed decreases (sometimes it stops downloading the blocks). Now, when the Number of blocks left: gets frozen, we think it's not updating anymore. But this is the time when Bitcoin core downloads the blocks at full speed.

The possible reason for boosting the progress is, that when we restart the Bitcoin Core, It shuts down without updating the number of blocks left. But, once we start the Bitcoin core again, it synchronizes the downloaded blocks first and then starts downloading the next blocks and the number of blocks left gets frozen again or updated very slowly. I assume it happens due to the low RAM or CPU power.

DAY 4

hero member
Activity: 1680
Merit: 845
Does it actually make any noticeable difference to the overall percentage though? I suspect what is happening is that when you restart you are simply interrupting the sampling process, and so when you restart Core thinks it is running faster than it is.
I've also noticed than restarting Bitcoin Core seems to boost the progress per hour, while indeed there's a difference in the total progress as well. However, I've noticed that it only last a few seconds and seems to get stuck after a while, and it seems to halt for a few seconds. From my understanding, it's purely visual and the halt is due to the start-up "boost" of a few seconds.
legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
Progress: (valid as of the creation date of this post)

Code:
Day 3:
Shishir99

Day 5:
oktana
spiker777

Day 6:
SilverCryptoBullet
apogio

Day 9:
Ultegra134
tech30338
DYING_S0UL

If you see any error in the progress report like your name isn't listed correctly, and so on, please let me know so I can fix it.
legendary
Activity: 2268
Merit: 18711
Mmm. But when I do this, I normally see little changes though. And it’s tempting to do when I see progress increase of 0.02 per hour.
Does it actually make any noticeable difference to the overall percentage though? I suspect what is happening is that when you restart you are simply interrupting the sampling process, and so when you restart Core thinks it is running faster than it is.
member
Activity: 97
Merit: 43
Day 6

Code:
{
  "chain": "main",
  "blocks": 798845,
  "headers": 825609,
  "bestblockhash": "000000000000000000015ac1274dfe28392050286cd7dae1242d2cc4a0eefbdb",
  "difficulty": 53911173001054.59,
  "time": 1689456577,
  "mediantime": 1689454326,
  "verificationprogress": 0.9091777796478837,
  "initialblockdownload": true,
  "chainwork": "00000000000000000000000000000000000000004eeb21f60f210841fcd62736",
  "size_on_disk": 4429001273,
  "pruned": true,
  "pruneheight": 796653,
  "automatic_pruning": true,
  "prune_target_size": 4999610368,
  "warnings": ""
}
hero member
Activity: 560
Merit: 1060
DAY 6:

Code:
{
  "chain": "main",
  "blocks": 825603,
  "headers": 825603,
  "bestblockhash": "000000000000000000037a262221634ffc442bc37c7c160358ec14e2225bba9f",
  "difficulty": 73197634206448.34,
  "time": 1705136961,
  "mediantime": 1705134951,
  "verificationprogress": 0.9999994427774004,
  "initialblockdownload": false,
  "chainwork": "000000000000000000000000000000000000000065637d5083a2efd3a452ed44",
  "size_on_disk": 614190288502,
  "pruned": false,
  "warnings": ""
}
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
it’s tempting to do when I see progress increase of 0.02 per hour.
I can't think of any reason why shutting down and restarting would improve things.

Quote
could it be the block it’s handling at the time?
You can check how long it takes to move up one block.

Quote
As for my CPU usage it’s currently below 10% (and the increase per hour is 1.30%)
It could be disk limited too. One way or another, restarting only adds extra work.
sr. member
Activity: 1680
Merit: 288
Eloncoin.org - Mars, here we come!
Sometimes the progress gets so bad I have to restart Bitcoin Core many times.
I don't think that helps. If anything, it makes it worse.
"Being slow" can have 2 main causes: slow internet, or slow hardware. If the problem is your internet, restarting Bitcoin Core won't help. If it's your hardware, all you can do is shut down other programs. Restarting a web browser can (temporarily) help to reduce it's memory consumption.

Mmm. But when I do this, I normally see little changes though. And it’s tempting to do when I see progress increase of 0.02 per hour. But based on a reply I saw here, could it be the block it’s handling at the time? Because I do use speed test (used this so much the previous night) and I can get 3MBS or like last night’s 15MBS. As for my CPU usage it’s currently below 10% (and the increase per hour is 1.30%) but if I get the slow progress again, I’ll check.
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
Sometimes the progress gets so bad I have to restart Bitcoin Core many times.
I don't think that helps. If anything, it makes it worse.
"Being slow" can have 2 main causes: slow internet, or slow hardware. If the problem is your internet, restarting Bitcoin Core won't help. If it's your hardware, all you can do is shut down other programs. Restarting a web browser can (temporarily) help to reduce it's memory consumption.
Jump to: