[bisq-network/bisq] High CPU Consumed (#4370)

cd2357 notifications at github.com
Sun Dec 13 19:21:02 CET 2020


> The DAO sync is running on userthread but the BSQ tx verification itself is super fast and the the problem. I think the problme is some client code reacting on state changes and doing expensive operations (e.g. lookups). There have been done some improvements already but I think there is more needed, but not a trivial task...

I suspect its the concurrent pricenode connections via tor. Last time I checked, tor connections go via some sort of io-blocking bottleneck. I noticed similar effects with the connections to the bitcoin nodes - connecting to them via clearnet caused less CPU overhead and was generally faster. Similar effect if I chose to use 1 tor bitcoin node, vs multiple (1 node was faster, smaller CPU spike). This was a few months ago, so not sure if it's still the case. But it might indicate that highly-active concurrent tor connections may cause/contribute to the CPU spike due to how multi-threading/IO is managed there.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/4370#issuecomment-744047458
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20201213/5388b981/attachment-0001.htm>


More information about the bisq-github mailing list