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

chimp1984 notifications at github.com
Wed Aug 12 22:33:17 UTC 2020


> > I still have problems with Firefox crashing regularly, and graphical heavy applications consuming like 50-90% of my CPU. I think this is unavoidable because of the lack of OpenGL (graphics libraries) in dom0, which Qubes devs say is a big security vulnerability, please let me know if you have a solution for this.
> 
> Sounds like you have a handle on the problem already! Seriously though, [memory problems](https://github.com/bisq-network/bisq/issues?q=is%3Aopen+label%3Ais%3Apriority+memory) are the biggest issue in Bisq UI at the moment and unfortunately seem to be inherent to the underlying (GUI) JavaFX library. For instance if you run the command line version of Bisq (seed_node) it consumes only 10% of the memory than the one that includes a GUI.
> 
> The most promising solution would be to use Bisq as a daemon running on the same box as your fullnode, and connect to its API via a lightweight client. This is not ready, but coming soon! (TM)

Those issues are all related to Linux versions. The RAM usage is likely a JVM setting issue, I have not followed the discussions but I think some people have found already something. I dont know about Qubes but might be that the JVM/JFX implementation has issues 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-673142783
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200812/1125c319/attachment.html>


More information about the bisq-github mailing list