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

[chimp1984]

> 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.

@oscarguindzberg Are you aware of any memory issues from BitcoinJ side at block download? Might be that it is only an issue on Linux (and maybe only at some distributions).

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