10
votes
Accepted
How to specify number of threads for bitcoind?
More threads will not make your software run faster.
Threads are used in order to be able to do more things concurrently, but not necessarily faster overall. Assume your internet connection allows ...
7
votes
Accepted
What is the maximum number of transactions per seconds on Bitcoin Cash?
The throughput in Bitcoin is not defined in transactions per second, rather indirectly, via block size limit. What matters in the size of transactions in bytes. The more complex the transaction is (...
4
votes
Accepted
Performance and modularity of Bitcore vs Toshi
Both are implementations of the Bitcoin protocol, however they are customized to make it easier to develop with. They are able to do this by storing all transaction and blockchain data in a database ...
4
votes
Bitcoin Core stalled peer logic during initial block download
During IBD, there is a "moving window" of 1024 blocks ahead from the current height, from which blocks can be requested from peers for parallel download. When a peer has an open slot for a ...
3
votes
Bitcoin Core really slow to sync recently
Nothing definitive, but figured out a few leads
Turned off the Antivirus, which might have been scanning newly downloaded files, it seemed to improve the speed, but it was still slower than expected.
...
3
votes
Why is initial block download slow on Raspberry Pi 4 with SSD?
My best guess is:
The RPi4 CPU is just way slower than the laptop CPU. They're both old designs (the RPi4 CPU from 2015, the laptop CPU from 2013), but the RPi4 one is significantly lower-power, and ...
3
votes
How to specify number of threads for bitcoind?
There's a difference between a software thread and a CPU thread. The number of threads that you are seeing is not the number of CPU threads that bitcoind is using. It is the number of software threads ...
3
votes
Accepted
What are the maximum useful memory limits for a Bitcoind full node?
After a point, there's no reason to increase memory usage further.
dbcache is useful up until the point where you have the entire UTXO in memory (4GB+ in 2021), and then increasing it further does ...
2
votes
What indexes does a Bitcoin Core node maintain to serve Bloom-filtered requests and SPV peers?
Bitcoin Core maintains an index of blocks and their locations on disk. When someone requests a block, it pulls the block from disk, and if they used BIP 37, it will run the block through the filter. ...
2
votes
How to increase the speed of synchronisation?
Next to installing an SSD, and using -dbcache=N to allow Bitcoin Core to take more memory, each release of Bitcoin Core has sped up the synchronization.
The upcoming Bitcoin Core 0.14.0 release will ...
2
votes
Warning: Reducing -maxconnections from 1000 to 865, because of system limitations
Connecting to more nodes will not make you learn about transactions faster, after some point.
Your node will just be busy processing messages - including many uninteresting ones - to maintain ...
2
votes
Does it make sense to create cryptocurrency based totally on go programming language?
I don't know how well it performs, but here is a full node implementation of Bitcoin in go-lang that you could investigate: https://github.com/btcsuite/btcd
2
votes
Accepted
Is the coinbase transaction the one and only means of minting new coins?
Is the coinbase transaction the one and only means of minting new coins?
Yes.
Is the coinbase transaction implicated in anyway in the creation of the first initial suppy of bitcoins or the creation ...
2
votes
Why is initial block download slow on Raspberry Pi 4 with SSD?
I can think of two possible reasons:
One, the CPU in the PI is much slower. The M92p uses an x86_64 CPU architecture, while the Pi uses an ARM CPU. CISC processors use more power, but are much faster ...
1
vote
Accepted
Mainnet node sync really slowly with 12 tb seagate external hdd says data rate is 6gb/s
Hard disk drives have been known to sync much slower than SSDs due to their slower read/write speed and higher latency. Even a SATA (non-NVMe) SSD will do a much better job. This also applies to RPC ...
1
vote
What do you think about "squashing" the blockchain?
Running a full node allows a user to independently verify the state of the bitcoin network. In order to verify the state of the network, the full node will run through every transaction in every block,...
1
vote
CVE-2012-2459 , possible code and performance improvement, is my logic correct?
Trigger warning: I'm not about to be nice. Because this code is responsible for my elevated blood pressure.
uint256 ComputeMerkleRoot(std::vector<uint256> hashes, bool* mutated) {
bool ...
1
vote
My bitcoint-qt client is crashing due to insufficient file descriptors repeatedly even after I set the ulimits to 65535
and the answer is....
if you use a shared folder on a VM the linux open file desc spec is irrelevant.
So I created a diskimage directly mounted in the host...
and voilà problem solved by avoiding the ...
1
vote
Accepted
Question about Vanitygen performance
Summit supercomputer has:
9,216 POWER9 22-core CPUs
Using CPU we have total 202752 cores to run, Vanitygen automatically use all threads to calculate, on average a CPU can generate 250k keys/sec on ...
1
vote
Regtest setup to analyze the protocol
I mean, is there a way to import the real bitcoin transactions on the blockchain into a private blockchain?
no
1
vote
How many MB of data does my bitcoin client have to download to be fully sync'd?
This is going to be date and transaction relative. For example if you setup a wallet today (June 5m 2017) it is about 120GB and most of that is from the last 4 years and moreso in the last several ...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
performance × 51bitcoin-core × 14
synchronization × 9
bitcoind × 8
blockchain × 5
network × 4
miner-configuration × 4
nodes × 3
hashpower × 3
transactions × 2
wallet × 2
client × 2
development × 2
signature × 2
full-node × 2
confirmations × 2
ecdsa × 2
cgminer × 2
gpu-mining × 2
scalability × 2
genesis-block × 2
raspberry-pi × 2
vanitygen × 2
time × 2
memory × 2