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

Devin Bileck notifications at github.com
Fri Jul 9 02:31:37 CEST 2021

Preliminary testing on Windows 10 using the VM arguments during a DAO resync:

- The memory usage fluctuating as the GC kicks in and it drops significantly. Just watching the task manager shows it getting up to around 2.5GB then dropping sometimes down to 1.5GB or so then ramping up.

- I do notice much more disk activity now as it is persisting to disk rather than remaining in memory, which hopefully will also help with possible corruption and invalid DAO states.

- I am noticing higher CPU usage now (averaging around 80% - up from around 50% or so). Not sure if that will have an impact or not.

I haven't yet evaluated whether there is a noticeable improvement to UI interaction during the DAO resync.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210708/8e09d88f/attachment.htm>

More information about the bisq-github mailing list