WIP: Release v2.3.0 #4
No reviewers
Labels
No labels
No milestone
No project
No assignees
2 participants
Due date
No due date set.
Dependencies
No dependencies set
Reference
Ronin/dojo!4
Loading…
Reference in a new issue
No description provided.
Delete branch "release/v2.3.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
1fccee04f2toa4888b3812Other changes are all ACK
@ -40,9 +40,13 @@ if [ "$BITCOIND_PERSIST_MEMPOOL" == "on" ]; thenbitcoind_options+=(-persistmempool=1)fiif [ "$BITCOIND_PERSIST_MEMPOOL" == "on" ]; thenThis if-block of code is already present right above it.
Fixed
@ -51,13 +55,28 @@ if [ "$BITCOIND_RPC_EXTERNAL" == "on" ]; thenbitcoind_options+=(-zmqpubrawblock=tcp://0.0.0.0:9503)fiif [ "$BITCOIND_BLOOM_FILTERS" == "on" ]; thenThis if-block of code activating peerbloomfilters is a regression.
Fixed
@ -25,3 +25,3 @@# Number of threads to service RPC calls# Type: integerBITCOIND_RPC_THREADS=12BITCOIND_RPC_THREADS=16This number deviated from upstream before, was this number already optimized for SBC's? Are there new findings regarding the effect of this parameter for SBC's?
Bitcoin Core v29 has raised the default to 16 threads so it seemed like a good idea to have it at 16 by default as well. RockPro64 has 6 cores (2 high-performance and 4 energy-efficient). Even on low-end devices like Raspi 4, the default setting should be at least double the count of CPU cores because some threads might be idle due to I/O and other reasons. With Dojo, indexer and explorer using RPC, I think it makes sense to raise this limit a bit. This change will not be applied for users who are upgrading, only for new installations.