About the graphs:
A lot of you may have noticed that your personal graph isn't updating very often. Others may not have seen much change at all, up to today.
It all comes down to rapid growth. There's about four times more active users than a few months ago and maybe an extra thousand in the last week. I may be way off with the exact numbers. I didn't keep track, but the message is the same. Getting lot's more users is great, but it can lead to growing pains.
One thing that's happening is that the auto updates to the graphs (run from cron) stop after about 2300 data files. These are run in the order they originally came from the JSON file which is sorted by hash rate. So, if your are in the top 2000+ hash rates on the site you have been getting regular updates. I'm not doing this by design. I've just discovered this is the way it's been working.
In the good old days, a week or so ago, there were fewer active users than that, and everyone got an update every 10 to 15 minutes. Right now we have over 4000 active users. (Active user means "Has a hash rate at the time the graph is run".) There are over 9000 total users who have stats and data files.
It can take, on average, a second to render a graph on my little server when it's under load. So, it can take over an hour to run graphs for all active users. Inactive users, who have no hash rate at the time the graphs run, are ignored for now.
If an auto update starts before the last one ends it can lead to a server lock up, so for now I've backed off auto updates to once an hour. That's for the lucky top half of the hash rates. I've also been running updates that will get the rest of the active users, but less often and only when I'm awake and at my desk in California.
This is temporary, and I'm working to lessen the pain, but I wanted to let everyone know what's going on.
A lot of you may have noticed that your personal graph isn't updating very often. Others may not have seen much change at all, up to today.
It all comes down to rapid growth. There's about four times more active users than a few months ago and maybe an extra thousand in the last week. I may be way off with the exact numbers. I didn't keep track, but the message is the same. Getting lot's more users is great, but it can lead to growing pains.
One thing that's happening is that the auto updates to the graphs (run from cron) stop after about 2300 data files. These are run in the order they originally came from the JSON file which is sorted by hash rate. So, if your are in the top 2000+ hash rates on the site you have been getting regular updates. I'm not doing this by design. I've just discovered this is the way it's been working.
In the good old days, a week or so ago, there were fewer active users than that, and everyone got an update every 10 to 15 minutes. Right now we have over 4000 active users. (Active user means "Has a hash rate at the time the graph is run".) There are over 9000 total users who have stats and data files.
It can take, on average, a second to render a graph on my little server when it's under load. So, it can take over an hour to run graphs for all active users. Inactive users, who have no hash rate at the time the graphs run, are ignored for now.
If an auto update starts before the last one ends it can lead to a server lock up, so for now I've backed off auto updates to once an hour. That's for the lucky top half of the hash rates. I've also been running updates that will get the rest of the active users, but less often and only when I'm awake and at my desk in California.
This is temporary, and I'm working to lessen the pain, but I wanted to let everyone know what's going on.
Appreciate the update. So even with the lack of updates to hash rate and other stats, we're still mining? I've been using 3333 just fine for the past two days at ~1.6Mh/s
Yup, the graphs, while nice, aren't essential to actual pool operation :] As long as your workers are reporting shares and aren't experiencing a ton of stales or disconnects then you should be fine
