Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CPU thread stuck on 100% post full synch (5.5.0) version #2795

Open
zkbitcoin opened this issue Jan 27, 2023 · 1 comment
Open

CPU thread stuck on 100% post full synch (5.5.0) version #2795

zkbitcoin opened this issue Jan 27, 2023 · 1 comment
Assignees

Comments

@zkbitcoin
Copy link

version 5.5.0
env linux
steps:

run wallet (pivxd) till full synch
run htop

100

@panleone
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

3 participants