[bisq-network/bisq] Optimize DaoState snapshot behaviour (#5609)

[chimp1984]

I tested with dao syncs and there memory goes up quite a lot. To avoid that gc is called too often (takes about 300 ms) I have set the totalMemory trigger to 3gb. This value is used at all the manual calls at areas where memory spikes are expected. Beside that there is a 10 min interval to check if totalMemory is > 1gb and invokes the gc if memory is high. 
With that more conservative approach memory will likely stay around 1 gb, but it avoids that gc gets called too often and as peak memory goes up to about 3gb a 1 gb level at usual operation should be ok.

-- 
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/pull/5609#issuecomment-875994678
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210707/967a6edc/attachment.htm>