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

[Nythain]

Pay per share has its ups and downs, just not as drastic as score and proportional. I made more in 12 hours on deepbit doing pps with my 68Mh/s a few days ago than i have in 2x as much time on either slush or eligius.

Well, don't take it personally, but my previous post was exactly about people like you .

Heh, I'm not taking anything personally. I don't want to see pps on your pool, and you're pool is my pool of preference. I'm also a complete and total newb to the scene, but I'm picking it up fairly decently.

Side note, good work and thanks for getting things back up and running and really smooth so quickly since getting back from holiday. As soon as I actually turn over enough for a payout there's definitely a donation coming your way from me.

[slush]

thanks for getting things back up and running and really smooth so quickly since getting back from holiday.

In fact, I started with repair immediately when I came home; I still had jacket and shoes when pool started to work again

[dbitcoin]

What happen?
On Saturday's evening (UTC), bitcoin daemons on two independent pool servers ate all available memory (RAM & swap) and fall to massive I/O operations, which make servers extremely slow. Central server switched traffic to the last machine, but this machine was unable to handle all traffic and some RPC calls started to timeout. Then those miners getting RPC timeouts probably started to ask server even more frequently (miners don't implement any "polite waiting" in the code and send new RPC call immediately after error/timeout). Those thousands of requests per second were the last piece to shut down last working machine .

Time for implement this (polite waiting) in miners?

[slush]

Time for implement this (polite waiting) in miners?

Yes, it would be very nice from miner developers...

[marcus_of_augustus]

Is it a known bug in the bitcoin daemon that initiated the failure cascade?

Or is it untraceable? Would be good to get some development work done on that too, no?

[slush]

Is it a known bug in the bitcoin daemon that initiated the failure cascade?
Or is it untraceable? Would be good to get some development work done on that too, no?

Initial problem was that bitcoind ate few GB of memory. It was first time I've seen that and cannot tell if it is bug or some kind of P2P attack as mentioned in my previous post.

[Cdecker]

cdhowie started implementing a nice proxy that would switch pools should it become unreachable: http://bitcointalk.org/index.php?topic=5506.0;all
We are also working on exponential backoff, so that the pools wouldn't get hammered all the time, until miners start implementing these features themselves this might be an option for serious miners

[molecular]

Lesson learn
a) Don't take holiday
b) If I'll take holiday, don't tell it anybody .
c) Try to setup watchdog restarting bitcoind when it started to use too much memory.

Man, option a) Is fucking sad! Don't do that.

[sniper_sniperson]

Maybe a small business partner or other worker to watch over pool when you are off-line?

A nice script that sends you SMS with current memory usage will do the job. Hard one is to find a working connection in some mountain regions

[warweed]

I'm certainly not complaining but what's happening here I haven't seen payouts like this since difficulty was in the 72k range


4292   2011-05-09 08:01:35   1:36:01   172239   1.47401750   122845    confirmed
4291   2011-05-09 06:25:34   1:15:57   131205   1.46427140   122834    confirmed
4290   2011-05-09 05:09:38   2:53:08   286294   1.57936660   122818    confirmed
4289   2011-05-09 02:16:30   0:47:36   73450   1.48812870   122789    confirmed
4288   2011-05-09 01:28:55   11:39:09   749522   1.41574380   122779    confirmed
4287   2011-05-08 13:50:02   16:05:01   526237   2.06949460    -    invalid
4286   2011-05-07 21:45:01   1:29:59   229074   0.98312942    -    invalid
4285   2011-05-07 20:15:03   0:02:10   6894   0.86713079   122515    confirmed
4284   2011-05-07 20:12:53   0:31:04   109518   0.79117583   122513    confirmed
4283   2011-05-07 19:41:49   0:43:54   161832   0.82696945   122511    confirmed
4282   2011-05-07 18:57:55   0:03:51   14381   0.72379974   122503    confirmed

[unxetas]

The pool's size is down considerably, so you're taking a much larger share of each block.. It's also taking longer to solve a block, obviously, but that looks pretty good to me

[BitterTea]

Slush, did you see davout's post regarding using monit to keep bitcoind up? http://bitcointalk.org/index.php?topic=5911.0

[warweed]

Wow yeah I didn't even notice the round tim :s lame

[dishwara]

4 hours still can't?
Current round duration:   3:50:42

[d0ct0r]

no block in 610k shares...
wow

[warweed]

Sorry slush when things get better I may come back but for now



Time for tyco to collect a percent  althou the image thing isn't overly accurate lol it jumps like 300 mhash/s

[sniper_sniperson]

Score - 1383977.1773

 

[Dayofswords]

no block in 610k shares...
wow

difficulty is a jerk.

[dishwara]

But if all are mining for current block only means then how can other pools solving blocks?
I think a bug is there, which instead of current block also counting the shares of all the blocks which got solved for the past 4 hours.
Seems locked somewhere which is still trying to solve one particular block while other pools solves blocks.

In deepbit many blocks solved.

[xenon481]

But if all are mining for current block only means then how can other pools solving blocks?
I think a bug is there, which instead of current block also counting the shares of all the blocks which got solved for the past 4 hours.
Seems locked somewhere which is still trying to solve one particular block while other pools solves blocks.

In deepbit many blocks solved.

The "bug" is called Variance.