Under high load, getGlobalStats can return > 5mb of data per message event. This causes the website rendering to eventually fail, live_stats eventsource to fail, and then eventually blows up the in-memory statsHistory objects.
This is caused by payments many hundreds of invidual payouts such as the case of the BTCP official mining pool.
Under high load, getGlobalStats can return > 5mb of data per message event. This causes the website rendering to eventually fail, live_stats eventsource to fail, and then eventually blows up the in-memory statsHistory objects.
This is caused by payments many hundreds of invidual payouts such as the case of the BTCP official mining pool.
https://github.com/BTCPrivate/z-nomp/issues/3
I've put in a temporary fix here:
https://github.com/BTCPrivate/z-nomp/pull/5/commits/7c55dc73a8fb225b76f10eb59b9dd8a1bd4363fd#diff-ea906d364558a45200106c6f2c92dc4aR385
I'm hoping you guys can figure out a more long term solution. There's a similar issue with worker data but that's not nearly as bad.
lotsofpayouts.txt