[bisq-network/bisq] Optimize initial data load (#1905)

[Manfred Karrer]

We changed the earlier behaviour with delayed execution of chunks of the list as it caused 
worse results as if it is processed in one go.
Main reason is probably that listeners trigger more code and if that is called early at 
startup we have better chances that the user has not already navigated to a screen where the
trade statistics are used for UI rendering.
We need to take care that the update period between releases stay short as with the current
situation before 0.9 release we receive 4000 objects with a newly installed client, which 
causes the application to stay stuck for quite a while at startup.
You can view, comment on, or merge this pull request online at:

  https://github.com/bisq-network/bisq/pull/1905

-- Commit Summary --

  * Replace containsKey with putIfAbsent call. Remove log.
  * Optimize processing of initial trade statistics and witness data

-- File Changes --

    M core/src/main/java/bisq/core/payment/AccountAgeWitnessService.java (4)
    M p2p/src/main/java/bisq/network/p2p/peers/getdata/RequestDataHandler.java (49)

-- Patch Links --

https://github.com/bisq-network/bisq/pull/1905.patch
https://github.com/bisq-network/bisq/pull/1905.diff

-- 
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/1905
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20181109/cd78ead8/attachment.html>