At least some of it looks like 1 significant figure only, which is not really enough resolution for a nice graph ;-) nOt sure why the "bestshare" is always 0?
It doesn't show the trailing zeros.Code:
{"hashrate1m": "0", "hashrate5m": "4T", "hashrate1hr": "447.94G", "hashrate1d": "4T", "hashrate7d": "0", "lastupdate": xxxxx, "workers": 1, "shares": xxxx, "bestshare": 0}
So in this case it's 4.00T
hashrate1m, hashrate7d and bestshare will be zero coz I changed it when I switched to the new server setup.
It used to just display the ckpool text files on the server (10s of thousands of them
)It now generates the file from CKDB which doesn't track bestshare (and probably never will since it's a meaningless random number) and doesn't pass hashrate1m or hashrate7d through to the web site.
ckpool doesn't use any form of database, just zillions of disk text files it updates all the time ... which I should remove from the code since it is a major I/O bottleneck when you have a real pool with lots of users and workers.
It is highly unlikely to repeatedly hit exactly a round hashrate of eg. 4.00TH/s. I really think this is a rounding issue. If you looked into the code, I am sure you would be able to confirm this?