You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Had finally some time to look at this issue and ran some profiling on my PC, results are:
Once wallet is loaded (so after block indexing) the thread which does basically all the job is ThreadMessageHandler subdivided in:
Around ~70% goes in ProcessMessage
and the remaining ~30% almost all in SendMessage
Then around ~82% of all ProcessMessage time is spent in ProcessMessageMasternodePayments + CMasternodeMan::ProcessMessage
... For comparison ~9% of ProcessMessage time is spent on ProcessNewBlock and ~2.5% in handle governance messages
So the bottleneck that stuck cpu is surely processing and sending masternodes data (in particular masternode list + masternode winners)...
Luckily for us the issue will be solved when we release v6.0 since all legacy masternode logic is going to be completely erased.
version 5.5.0
env linux
steps:
run wallet (pivxd) till full synch
run htop
The text was updated successfully, but these errors were encountered: