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
Comments
Ok, even better since v1.2.3 I don't have any Bitcoin network peers using local |
Same problem here while working with local bitcoind: around 150% cpu usage on average. |
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 |
@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. |
@darosior Is your local bitcoind node running in pruned mode? If you use latest bitcoind release, you need to enable bloomfilter support. |
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
nop
Will try, but why don't you use RPC for localhost's bitcoind ? |
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? |
Will edit with a @tasoshi above runs a Ubuntu Bionic (don't know his Kernel though). No VM. We have different setups, and same symptoms. |
Ok, that was the bloom filters apparently........ Thanks @chimp1984 ! |
@darosior Did you use latest bitcoind where bloom filters are not supported by default? Or otherwise can you specify what was the issue? |
Description
Bisq with local bitcoind consumes around 100-120% of CPU (
top
return), while it consumes 10 to 15% with a remotebitcoind
(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
.The text was updated successfully, but these errors were encountered: