|
Title: [POLL] How long to sync on an initial core install Post by: d4n13 on January 09, 2018, 02:30:13 AM Performing a fresh install on a very wimpy computer. It's syncing now and will look to take between 1-2 weeks to sync. I know this is way outside the bell curve and I'm far far below the minimum install requirements, so... Wanted to know how long a propper install takes to perform. I'll give the form for the reply data, if anyone cares to fill it out:
Quote Rules: Fresh installs with no pre seeded block data or levelDB data
Here's my my config (I know... its wimpy and well below the minimum requirements)
Title: Re: [POLL] How long to sync on an initial core install Post by: jnano on January 09, 2018, 11:33:45 PM A different OS, and you practically have no RAM, but if you could spare more RAM, see if putting the chainstate directory on a RAM drive helps:
https://bitcointalk.org/index.php?topic=2291857.0 Title: Re: [POLL] How long to sync on an initial core install Post by: d4n13 on January 15, 2018, 07:00:51 AM How big is the chainstate database? I know it changes everyday, but I can't get a clear answer.
I hear the uncompressed UTXO database (as of today) is around 4 GB, and that the chainstate (compressed) is around 2 GB. Does this sound right? Title: Re: [POLL] How long to sync on an initial core install Post by: LoyceV on January 15, 2018, 09:22:36 AM I've tested this a while back:
Duration: maybe 20 hours Date: say 2 months ago Version: Bitcoin Core v0.15.1.0 Headless: Running Bitcoin Core Pruning: Pruning enabled for the test, -prune=550 dbcache: unchanged default options maxmempool: unchanged default options bandwidth: standards DSL, kinda irrelevant for this test DiskIO: very high, I saved this to a ramdrive (/run/shm) CPU: 3 year old Intel i3 laptop Memory: 12 GB, up to 50% OS: 64 bit Linux In my experience, there's 2 bottlenecks for Bitcoin Core: total RAM for file cache, and access time to your disk. For practical use, I now have my chainstate-directory on an ssd, and my blocks-directory on a (much bigger) hdd. I assume you're using cloud hosting considering your specs. If you want this to be faster, you could add more ram/cpu during syncing. Title: Re: [POLL] How long to sync on an initial core install Post by: jnano on January 15, 2018, 08:04:41 PM How big is the chainstate database? I know it changes everyday, but I can't get a clear answer. With Bitcoin Core's native storage format, mine is about 3,780,000,000 bytes as of a few days ago.Trying solid LZMA compression on 2% of the data, I got a reduction of 25% with solid compression, and 19% without. With ZIP compression (32KB blocks) I get 15%. Is there any RAMdrive software with a configurable compression block size? Title: Re: [POLL] How long to sync on an initial core install Post by: d4n13 on January 15, 2018, 08:37:40 PM ... Duration: maybe 20 hours ... Pruning: Pruning enabled for the test, -prune=550 ... DiskIO: very high, I saved this to a ramdrive (/run/shm) ... OS: 64 bit Linux ... Yep... saw your post on /run/shm and tried the same. Spun up a full size server (2xCore 13GB mem) and sync too 20.16 hrs out of ramdisk. Title: Re: [POLL] How long to sync on an initial core install Post by: achow101 on January 16, 2018, 06:57:28 AM It will sync faster and have less disk I/O if you increase the dbcache. This requires more RAM though. Raising the dbcache to anything larger than 8000 MB (-dbcache=8000 is large enough to store the whole thing in memory and then flush right at the end so there's significantly less disk I/O then. Of course you will need plenty of RAM in order to set the dbcache to that high.
Title: Re: [POLL] How long to sync on an initial core install Post by: jnano on January 16, 2018, 05:48:19 PM Compared with version 0.15.0.1, did 0.15.1 change in any way the caching or disk I/O logic?
Title: Re: [POLL] How long to sync on an initial core install Post by: d4n13 on January 20, 2018, 06:08:14 AM It will sync faster and have less disk I/O if you increase the dbcache. This requires more RAM though. Raising the dbcache to anything larger than 8000 MB (-dbcache=8000 is large enough to store the whole thing in memory and then flush right at the end so there's significantly less disk I/O then. Of course you will need plenty of RAM in order to set the dbcache to that high. Only data I can find on the UTXO set shows it's closer to 4GB (https://statoshi.info/dashboard/db/unspent-transaction-output-set) instead of 8GB. Am I looking at the on-disk size (compressed) compared to the in-memory size? Title: Re: [POLL] How long to sync on an initial core install Post by: achow101 on January 21, 2018, 03:27:25 AM Compared with version 0.15.0.1, did 0.15.1 change in any way the caching or disk I/O logic? No.Only data I can find on the UTXO set shows it's closer to 4GB (https://statoshi.info/dashboard/db/unspent-transaction-output-set) instead of 8GB. Am I looking at the on-disk size (compressed) compared to the in-memory size? That's the on disk sized which is compressed. The in memory size is much larger, ~7-8GBTitle: Re: [POLL] How long to sync on an initial core install Post by: d4n13 on January 23, 2018, 10:20:16 PM Only data I can find on the UTXO set shows it's closer to 4GB (https://statoshi.info/dashboard/db/unspent-transaction-output-set) instead of 8GB. Am I looking at the on-disk size (compressed) compared to the in-memory size? That's the on disk sized which is compressed. The in memory size is much larger, ~7-8GB[/quote] So as a WAG, I'll just double what the on-disk size reported from the report. Won't be precise, but better than nothing I suppose. Thx Title: Re: [POLL] How long to sync on an initial core install Post by: jrian on January 31, 2018, 11:18:57 AM Duration: 8-12 hours
Date: 2017-2018 Version: latest Headless: Yes, bitcoind Pruning: no bandwidth: 1000 Mbit/s CPU: XEONs Memory: 8-128 OS: Unbuntu/Debian |