[bisq-network/bisq] ConcurrentModificationException FileManager::saveToFile (#3752)

[chimp1984]

Thanks @julianknutsen for the work on that!

I think performance optimisation in the DaoState is required anyway (and I saw some work has started there). 

For the nr. 2 and 3 of the performance bottleneck candidates (tradestats, account age witness) I think we should look into a solution to split up the historical data and only keep the most recent data as dynamic data structure which would become much smaller (I estimate a few % of the current data size). As those data are "append only" and carry much less complexity than the DAO domain I think that might be a good candidate for improvement.

SequenceNyMap uses a max size, we might consider to lower that so it decreases the object size and with it the CPU costs for persisting. Also tuning of the persistence intervals can help here.

Preferences should not be written to disk often, if so, we should find out why and fix it if its not required. Also here we can increase peristence interval.
  

-- 
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/3752#issuecomment-564604079
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191211/e262467d/attachment.html>