[4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool

[allinvain]

Ahhh...ok, I get it.  So if a round is 3 hours, there may have been multiple blocks found in that 3 hour span, but that's how long it took the pool to find a block.

Makes perfect sense, gracias

Yep essentially a round is how long it takes the pool to find a block.

[1713872940]

1713872940

[1713872940]

1713872940

[1713872940]

1713872940

[allinvain]

Slush, you working on the pool?  Lot of connection problems in the last 10-15 mins.

Hmm, message said that the server is down for maintenance.

[slush]

I've troubles with database, pool was down for ~20 minutes. I modified database configuration, should be better next time.

[allinvain]

I've troubles with database, pool was down for ~20 minutes. I modified database configuration, should be better next time.

Well if there is one thing that I've learned about bitcoin mining pools is that they're not exactly easy on server resources and it seems it's quite a challenge to keep a pool running without any problems. Also let's not forget the potential for getting DDoS'ed too!

[slush]

Well if there is one thing that I've learned about bitcoin mining pools is that they're not exactly easy on server resources and it seems it's quite a challenge to keep a pool running without any problems. Also let's not forget the potential for getting DDoS'ed too!

Amen.

[dikidera]

How soon before long polling?

[SchizophrenicX]

is anyone having the problem communicating thing again?

[Jack of Diamonds]

2011-06-03 19:13:42: Listener for "worker41": 03/06/2011 19:13:42, Problems communicating with bitcoin RPC
2011-06-03 19:13:47: Listener for "worker18": 03/06/2011 19:13:47, Problems communicating with bitcoin RPC
2011-06-03 19:14:36: Listener for "worker27": 03/06/2011 19:14:36, Problems communicating with bitcoin RPC
2011-06-03 19:14:51: Listener for "worker22": 03/06/2011 19:14:51, Problems communicating with bitcoin RPC
2011-06-03 19:15:06: Listener for "worker29": 03/06/2011 19:15:06, Problems communicating with bitcoin RPC
2011-06-03 19:15:53: Listener for "worker39": 03/06/2011 19:15:53, Problems communicating with bitcoin RPC
2011-06-03 19:16:17: Listener for "worker16": 03/06/2011 19:16:17, Problems communicating with bitcoin RPC
2011-06-03 19:17:25: Listener for "worker02": 03/06/2011 19:17:25, Problems communicating with bitcoin RPC

[anisoptera]

How soon before long polling?

This. I have almost 5% stale rate and tons of work queue is empty

[slush]

I finally have response from Linode guys, they decided to raise limits for pool significantly. Unfortunately it need balancer restart to take effect, so expect short outage.

This should solve stale rate and RPC errors (but today's errors were caused by database error, which is already solved).

EDIT: Great, looks like that annoying packet loss is solved! (0% in 2000 requests)

[slush]

How soon before long polling?

You have no idea how long I spent on tracking issues of last days . Now I'm closing myself in the office and going to continue on LP

[slush]

By the way, there is another guy with access to pool servers. He's currently learning how to fix some specific problems for times when I'm offline. He is very trustworthy for me and well known on this forum, but he doesn't want to reveal his identity; he simply doesn't have enough time for 'normal agenda' like responding emails, replying on forum and so on. But this independent supervision is definitely making operator's response faster in case of any problem.

[datguywhowanders]

Thanks Slush!

[MiningBuddy]

I finally have response from Linode guys, they decided to raise limits for pool significantly. Unfortunately it need balancer restart to take effect, so expect short outage.

This should solve stale rate and RPC errors (but today's errors were caused by database error, which is already solved).

EDIT: Great, looks like that annoying packet loss is solved! (0% in 2000 requests)

Just want to say thank you Slush, the connection stability and overall responsiveness has been greatly increased  
There are still some issues with idle miners, but it is a lot better then before.

[amazingfunksta]

Hey slush, I was just wondering why my share was so low on this round.

http://img.photobucket.com/albums/v93/amazingfunksta/why.jpg

Thanks ^_^,

[pokermon919]

Hey slush, I was just wondering why my share was so low on this round.



Thanks ^_^,

same here, that round was unusually low for me. I think maybe the pool had a dc problem.

[Jack of Diamonds]

I didn't notice a significant decrease of earnings on block 5081 although it was in general about 30% less than usual.

However, error messages have dropped from hundreds per hour to about 5 or less per hour. So slush is doing something right with server upgrades.

[Meatball]

Ooofah, cluster performance over 700 GH/sec, wasn't it under 500 just a week or so ago?

[MiningBuddy]

I didn't notice a significant decrease of earnings on block 5081 although it was in general about 30% less than usual.

However, error messages have dropped from hundreds per hour to about 5 or less per hour. So slush is doing something right with server upgrades.

Yeah its much better, but the pool size is increasing so more shares = less payment, but that can also mean faster block finding. Although, remember there is still the luck factor.

[slush]

Hey slush, I was just wondering why my share was so low on this round.

Damn, I always forget to check if score renormalization finished when there're database problems. I fixed rewards, should be fine now.