I’m combating poor efficiency of Bitcoin Core full node operating as, which is used as a scorching pockets.
There are comparable questions already however with out a solution or resolution
Bitcoin core is freshly put in a few month in the past (model 24.0.1), new pockets is created on that node a couple of weeks in the past as nicely. This pockets is a HD pockets and it makes use of “descriptors” format (not the legacy one).
I generated about 300k addresses from this pockets and imported about 10k non-public keys within the descriptor format.
The pockets responds fairly fast total however typically it caught and nearly any name final for tens of seconds or for minutes. getbalances, listtransactions, and so on.
Additionally, validateaddress util name final for tens of seconds and it results in learn timeouts in my purposes.
There’s an instance of that subject (with legacy deal with):
$ time bitcoin-cli validateaddress 1Hv...qK
{
"isvalid": true,
"deal with": "1Hv...qK",
"scriptPubKey": "76a9...88ac",
"isscript": false,
"iswitness": false
}
actual 0m46,627s
person 0m0,007s
sys 0m0,000s
Throughout that point, b-httpworker.X consumes 100 % CPU and there’s no peak in IO nor RAM utilization. If I repeat that decision afterwards, it returns the response immediately.
validateaddress ought to simply examine the deal with format, should not it? I do not perceive why it final so lengthy and what does it do throughout that point. debug log is, sadly, empty.
Does anybody has a clue what’s going on? How ought to I debug such issues?
Thanks for assist.