1) live stat will harm multipoolminer because it will switch algo continually if there's no internal threshold
2) multipoolminer already made big ddos like traffic to server before and made things unresponsive.
Imagine 100000 miner rigs are all polling web server continually.
It's not running per one user, per rigs.
Polling massive amounts of rigs is far from ideal at all.
We should make some socket connecttion to get realtime api data if you really need realtime data.
I added "last_block" field at getminingandprofitsstatistics api as you requested.
It's unixtimestamp number.
1. There is an internal treshhold already in place, MPM can evaluate real-time data it receives and needs the same to do so accurately and timely.
2. Even though you have a valid point here, high traffic on API is completely normal and just something all operators need to accept. The increase in traffic is parallel with your earnings. MPM does not just poll the API for no reason, these are all users mining on your pool. Improvements are definitely needed. I am not saying it should be real-time, updating every 1-3 minutes is still fine, however having to rely on 30-minute-old data is just redonkulous in a fast-paced crypto world.