Closed theicosuperman closed 6 years ago
Javascript is handled on cliënt side, so this can be normal..
I did this in config.json "stats": { "updateInterval": 0.1, "historicalRetention": 172800, "hashrateWindow": 30 },
Unfortunately I don't know how to make graph update more often. Is this possible?
You set it to hold 2 days worth of info; used 30 seconds as your time of "seconds worth of shares should be gathered to generate hashrate"; and "gather stats to broadcast to page viewers and store in redis for historical stats" at a rate of 10 times per second, and you're confused as to why it pegs the CPU?
and now you want it to update more often than that?
Wow, I completely missed out updateInterval time stretch. for now I understand what was really wrong. Thank you for explanation. After I turend "updateInterval": to 1, I don't see this cpu load no more. Btw redis ops/s was more than 200 in this setting.
Firefox is hanging up, opera is working but slowly.