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

*High* CPU usage with local bitcoind #3593

Closed
darosior opened this issue Nov 10, 2019 · 10 comments
Closed

*High* CPU usage with local bitcoind #3593

darosior opened this issue Nov 10, 2019 · 10 comments

Comments

@darosior
Copy link

Description

Bisq with local bitcoind consumes around 100-120% of CPU (top return), while it consumes 10 to 15% with a remote bitcoind (federation's ones if I don't make a mistake ?).

Version

v1.2.3 but all prior were also affected.

Steps to reproduce

Just try running Bisq with a local bitcoind.

@darosior
Copy link
Author

Ok, even better since v1.2.3 I don't have any Bitcoin network peers using local bitcoind while I have some using federation's bitcoind

@tasoshi
Copy link

tasoshi commented Nov 27, 2019

Same problem here while working with local bitcoind: around 150% cpu usage on average.

@darosior
Copy link
Author

darosior commented Dec 1, 2019

Ok so it seems to be related to "full" nodes: https://docs.bisq.network/dao-technical-overview.html#full-nodes. It might be that we Bisq starts as a "full" node by default if it detects a bitcoind runnning ?

@chimp1984
Copy link
Contributor

@darosior No by default a Bisq node runs a lite node. You need extra configurations to run a full DAO node. At startup it syncs with past DAO blocks, that can take a while if the app was not used for a while. After the DAO sync is done CPU should go back to normal.

@chimp1984
Copy link
Contributor

chimp1984 commented Dec 1, 2019

@darosior Is your local bitcoind node running in pruned mode? If you use latest bitcoind release, you need to enable bloomfilter support.

@darosior
Copy link
Author

darosior commented Dec 1, 2019

After the DAO sync is done CPU should go back to normal.

I've used it for 3 months with CPU usage at 100%. With an approximate up time of 6 hours a day, I'd say it isn't due to initial sync. Moreover why would it take more CPU power with a local bitcoind

Is your local bitcoind node running in pruned mode?

nop

f you use latest bitcoind release, you need to enable bloomfilter support.

Will try, but why don't you use RPC for localhost's bitcoind ?

@chimp1984
Copy link
Contributor

This is weird... Usually CPU is about 2-4% after initial sync. Seems some environments cause some issues. Can you post info about your setup (OS, ram,...)? Do you run inside a VM?

@darosior
Copy link
Author

darosior commented Dec 2, 2019

Will edit with a uname -a but I run a Debian Buster with a 4.19 Kernel. No VM.
Edit: 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20) x86_64 GNU/Linux

@tasoshi above runs a Ubuntu Bionic (don't know his Kernel though). No VM.

We have different setups, and same symptoms.

@darosior
Copy link
Author

darosior commented Dec 2, 2019

Ok, that was the bloom filters apparently........ Thanks @chimp1984 !

@darosior darosior closed this as completed Dec 2, 2019
@chimp1984
Copy link
Contributor

@darosior Did you use latest bitcoind where bloom filters are not supported by default? Or otherwise can you specify what was the issue?

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

No branches or pull requests

3 participants