[bisq-network/bisq] Startup problem on slow/degraded networks (the "3/4" problem) (#2547)

[agb19]

Hi @ManfredKarrer, the fix in PR #2583 works, with some limitations.

In token-bucket simulations, the resistance to network degradation has improved by ~50% as expected, which confirms that the fix does indeed act on the source of the issue. 

In real-life conditions, and specifically in my "worst case scenario" network, the improvement is unfortunately insufficient to push the startup sequence over the initial `PreliminaryGetDataRequest`  / `GetUpdatedDataRequest` hurdles. 

I tried gradually increasing the timeout numbers from PR #2583 and found a sweet spot around **300 seconds** (5 minutes). This setting seems to work well to achieve the "expected result" above: the application takes a while to start up, but it does so eventually, even on a degraded network, and once the initial hurdle is cleared, the operation is smooth. 
I have tested the 300 second mod on versions 0.9.5-0.9.8, on normal and degraded networks, and it worked well for me with no side effects, however I am reluctant to recommend this change as I don't fully understand its impact. 

-- 
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/2547#issuecomment-481957472
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190410/3838bc60/attachment.html>