Good to know...and thank you for the work you have been doing.
+1
What he said
Topic: [1200 TH] EMC: 0 Fee DGM. Anonymous PPS. US & EU servers. No Registration! - page 193. (Read 499491 times)
August 19, 2011, 11:00:28 AM
+1
What he said
August 19, 2011, 10:19:54 AM
Good to know...and thank you for the work you have been doing.
Hopefully this will stop the disconnects I have been getting when long polling ends. I hate waking up in the morning to find that my rigs shifted to the backup due to disconnects.
Hopefully this will stop the disconnects I have been getting when long polling ends. I hate waking up in the morning to find that my rigs shifted to the backup due to disconnects.
August 19, 2011, 10:03:10 AM
Someone get a big stick.
But it's true, I haven't been able to game for the past two or three days!
I've confirmed a NIC problem on the DB server. I will need to bring the server down to replace it.
I will be moving the server to another rack at the same time and replacing both NICs with some more reliable Intel ones. You should see a very slight increase in response time to the server (translating into slightly less stales).
I will be doing this today instead of next week like planned. I will probably bring the server down in about an hour, so around 10 AM CST (15:00 UTC). I hope for downtime to be less than 30 minutes. But it's better than having intermittent drop outs for no apparent reason all weekend.
But it's true, I haven't been able to game for the past two or three days!
I've confirmed a NIC problem on the DB server. I will need to bring the server down to replace it.
I will be moving the server to another rack at the same time and replacing both NICs with some more reliable Intel ones. You should see a very slight increase in response time to the server (translating into slightly less stales).
I will be doing this today instead of next week like planned. I will probably bring the server down in about an hour, so around 10 AM CST (15:00 UTC). I hope for downtime to be less than 30 minutes. But it's better than having intermittent drop outs for no apparent reason all weekend.
August 19, 2011, 07:32:35 AM
I'm so pissed of right now I'm going to hold my breath until this block is solved! Damn it!
August 19, 2011, 02:08:34 AM
Inaba's been busy adding new graphs instead of playing games.
Stop with the feature requests, damn it!
August 19, 2011, 01:01:54 AM
I thought the last round was bad....
August 18, 2011, 09:30:48 PM
Hey Inaba, I vaguely recall you thought about providing some kind of incentive for top miners. I'm assuming you've dropped that? Variance is starting to make me think about trying a larger pool.
August 18, 2011, 09:19:56 PM
I've added two new graphs and combined them with the daily hashrate graph. It's now called Historical Hashrate Graph.
I'll work on adding links to the pages to other graphs next.
I'll work on adding links to the pages to other graphs next.
August 18, 2011, 04:00:34 PM
@Inaba Hey thanks for taking the time to answer and ask the questions.. It's appreciated.
August 18, 2011, 03:37:58 PM
Ok, userstats should be back in the API now.
August 18, 2011, 10:45:30 AM
I responded in your thread. My point still stands and is still valid unless there is something new and interesting that you've come up with that no one else has to reduce latency.
August 18, 2011, 10:01:37 AM
They modify their getwork server to report less rejects/stales. There's no mystery there. I can do the same here if it'll make you feel better, though. I can, in fact, using their methods, give you 0 rejects.
PPS is the only reward type that trick wouldn't work for. For a full rebuttal, see https://bitcointalksearch.org/topic/m.465303 August 18, 2011, 02:27:17 AM
EDIT: whoops wrong thread...
August 17, 2011, 11:40:10 PM
Indeed. Well, the "rejects" you see in the terminal aren't really rejected in the literal since. They are accepted and found to be invalid for one reason or another and reported as rejected. It's fairly easy to turn that off and just report accepted for every share, regardless of its' true disposition in finding a block.
Some pools (eg eligius) report rejects separately as 'stale' and 'invalid' - maybe that might clear some of these misconceptions up?
August 17, 2011, 11:26:44 PM
I apologize for the downtime. I noticed a problem with the MySQL database and in the process of diagnosing it, I decided to reboot the server which turned out to be a bad idea.
After the server came back up, I continued diagnosing the problem and identified two separate issues causing slow queries on the DB. I've completely fixed one I believe, the other one is related to the user stats in the API.
I need to do some code rewriting for that, as such, worker stats in the API (yeah, the same thing I just fixed earlier today, which is why the problem just showed up) are disabled until I get it rewritten. Possibly tonight, but more likely tomorrow.
I apologize for the inconvenience... I guess the user stats hadn't been working since I made a change a few days ago and when I fixed the api to accommodate the change today the old method of calculating stats puts the new table under too big a strain.
I believe this is also the cause of the intermittent Can't connect to RPC errors some of you noticed as well, so this should eliminate that as well. Three bugs fixed for the price of one! Bonus... err wait..
After the server came back up, I continued diagnosing the problem and identified two separate issues causing slow queries on the DB. I've completely fixed one I believe, the other one is related to the user stats in the API.
I need to do some code rewriting for that, as such, worker stats in the API (yeah, the same thing I just fixed earlier today, which is why the problem just showed up) are disabled until I get it rewritten. Possibly tonight, but more likely tomorrow.
I apologize for the inconvenience... I guess the user stats hadn't been working since I made a change a few days ago and when I fixed the api to accommodate the change today the old method of calculating stats puts the new table under too big a strain.
I believe this is also the cause of the intermittent Can't connect to RPC errors some of you noticed as well, so this should eliminate that as well. Three bugs fixed for the price of one! Bonus... err wait..
August 17, 2011, 09:41:39 PM
I wonder if I should set my backup to solo mine just on the chance that I might get really lucky 
August 17, 2011, 08:48:12 PM
The pool is having a hardware issue. It will be back up in about 30 - 45 minutes while I replace the failed part.
August 17, 2011, 07:58:48 PM
I always thought there was something about their server that was working better.
Doesn't matter now. I used to have one card on Eclipse and the other on Triple each using the other pool as backup.
Then Hoppers with hundreds of GH/s would jump in and I was getting too little for my efforts. So I switched both cards to Eclipse.
Our rate goes up and down here but not like it did at Triple. Looks like a lot of miners have pulled out of there. They're under 18 GH/s as I type this.
Doesn't matter now. I used to have one card on Eclipse and the other on Triple each using the other pool as backup.
Then Hoppers with hundreds of GH/s would jump in and I was getting too little for my efforts. So I switched both cards to Eclipse.
Our rate goes up and down here but not like it did at Triple. Looks like a lot of miners have pulled out of there. They're under 18 GH/s as I type this.
August 17, 2011, 07:51:44 PM
Indeed. Well, the "rejects" you see in the terminal aren't really rejected in the literal since. They are accepted and found to be invalid for one reason or another and reported as rejected. It's fairly easy to turn that off and just report accepted for every share, regardless of its' true disposition in finding a block.
August 17, 2011, 07:49:30 PM
So when I thought I was getting 0 rejects at Triplemining there were rejects while accepted was scrolling up the terminal?!
Jump to: