Last time i checked, multi-core only enabled on signature verification, so there's nothing you could do beside wait patiently.
See https://bitcointalksearch.org/topic/concurrent-validation-engine-for-bitcoin-core-5103538 for more info.
Topic: [btc] (Read 194 times)
From the configuration shared in OP, the dbcache is set to 20000 which is way too much, in my opinion.
If he has 32GB of RAM and more, there's no harm on using a high cache size.The problem in the config is par=15 which limits his system on using 15cores while the default "0" will use all available cores if needed.
For the issue, OP might had just started the -reindex when he posted this thread.
At which point that there're no signature validation required for earlier blocks thus wont require a lot of CPU usage.
If not, there must be a bottleneck somewhere.
...
If he finds a way to make bitcoin-qt uses more cores, will this really speed up the rescanning process? I doubt it will!Setting the dbcache value properly and using an ssd would be enough.
From the configuration shared in OP, the dbcache is set to 20000 which is way too much, in my opinion.
As far as I know and have seen it's locked to one core. Some people have hacked together ways around it but you would have to dig. I had a similar issue a year or so ago and in the end just said screw it and let it run for hours till it finished.
Others might be able to give you better advice, but I would just let it run. If you stop it and start again with other parameters and they don't work you just lost all the time it was running now.
-Dave
Others might be able to give you better advice, but I would just let it run. If you stop it and start again with other parameters and they don't work you just lost all the time it was running now.
-Dave
Jump to: