[bisq-network/bisq] Update seednode config to increase resource limits for v1.2 (#3545)

chimp1984 notifications at github.com
Tue Nov 5 03:21:39 UTC 2019


@wiz At 1.2.0/1.2.1 we have an issue with the trade statistics which caused a lot of resources as each node got delivered 7-9 MB of data. That was fixed with the branch I provided and now memory consumption should be back to normal. I am not aware of any reason why v1.2 should consume more ram as before. 

There was the issue that risq (as discused with @bodymindarts and you) made requests which caused seeds to respond with about 10 MB of data (all accountage witness data and all trade stats) but those have been about 10 requests a day so that should not have caused permanent memory/cpu pressure, but could have been the cause for an OOM error as well. I have not tested the performance cost here but I know from BSQ blocks that requesting so much datat was very heavy (took about 30 sec for 12MB data). 


Looking at https://monitor.bisq.network/d/qclhStdWz/server-metrics?orgId=1&from=now-90d&to=now&var-Server=fl3mmribyxgrv63c

With a 90 days history it seems we got higher memory consumption around the 15th of September. That was around 1.1.6 release. But different seeds have different patterns, but all had lower memory consumption back in August. So some changes in that time frame has caused more pressure. 1.1.6. introduces traders chat, so that produces more mailbox messages and currently there are about 600 which is rather high, but probably caused by the update mess....
 
We should monitor those data more closely and alert devs in case we see some increases....

I will try to look into code changes in 1.1.6. which might be responsible for those changes.

-- 
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/3545#issuecomment-549646285
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191104/ea959034/attachment.html>


More information about the bisq-github mailing list