[bisq-network/bisq] Node becomes unresponsive causing all peers to be dropped (#3143)
notifications at github.com
Tue Aug 27 09:17:22 UTC 2019
It seems to be as if they are all unique proposals remove requests. In general that shouldn't degrade the performance just having this many proposals to be removed from your local store. But it might trigger some complex UI update logic for each removal. I have to look into this in more detail.
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...
More information about the bisq-github