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

[Stan]

>From @crocket 
> A few minutes after startup, bisq-desktop stops consuming a lot of CPU resource and its GUI becomes useable.
> But, the GUI is not nearly as responsive as firefox or brave web browser.

A long chain sync at startup locks up the UI thread until it's done, gobbles `off heap memory`, and doesn't give it back to the OS until Bisq is shutdown.  The most impolite off heap memory usage happens when you start Bisq on a new, completely empty data directory, or when starting Bisq after an extended period of time of not running it -- it has to perform another long chain sync. 

This is a problem I have not been able to solve.  

The only way I know of giving the large amount of off heap memory Bisq used to sync the chain back to the OS: 
Shut Bisq down after a long sync is complete, then restart it.  The UI will be more responsive after starting it the 2nd time.

>From @crocket 
> Are you telling me to assign more RAM to JVM?

Don't fiddle with the jvm ram options.  I'll expain more in some of the following comments.

-- 
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-744027049
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20201213/425201c0/attachment.htm>