Ok, the surge has passed. By the way, if your recent share submission rate is less than 40%, you will only get solo shares Tongue

. Don't want to get the pool banned for DoSing getworks with no shares returned - this protection worked very well just now.

Quote from: shamen on June 24, 2011, 06:48:35 PM

I cant seem to connect any more Sad

*edit* back upp. offline for about 2 hours for me there Sad

Server crashed after running out of memory. Spent some time optimizing the database - replaced a large number of hashtables with arrays - cut the memory usage in half. Also, bitcoind needs restarting occasionally - its memory footprint can grow larger with time than that of Firefox 3!

Quote from: TeaRex on June 24, 2011, 05:52:06 PM

Hello Multipool,

my total efficiency value suddenly jumped way up after today's difficulty change. Is your website script maybe not taking into account that older shares have to have their efficiency measured against the difficulty that was in place when they were submitted rather than the current value?

Regards TeaRex

That's right. I thought I put the variable difficulty checks in place already, but apparently I didn't. The checks are up now, and all your efficiencies are accordingly back down. Are you sure you wouldn't rather be looking at 170% efficiency values, even if only imaginary Cheesy

Quote from: superweb on June 24, 2011, 04:10:07 PM

I can see now is, that my stale rate is much higher than when I mined on single pool. Used to have it at about 0,5%, now with 52 stales from 3700 shares I'm at about 1,4%
Is this normal?

Yes, unfortunately that's the downside of a mining proxy. With the extra hop in both directions, getworks and shares have greater age, and therefore have higher chance of arriving after a block change and being rejected. Multipool has longpolling to minimize stale shares, but even so it takes time for the pool to be notified of a block update and then notify the miners. Of course, all this takes place within an interval of a few seconds.

On the other hand, I occasionally see shares that are clearly within a block, have valid merkles and nonces, have a valid hash, and are not duplicates, but that nevertheless get rejected by the target pool, even as many other shares of similar age get accepted around the same time. Why does this happen? Couldn't really tell without knowing the internal workings of the other pools.