Topic: [~1000 GH/sec] BTC Guild - 0% Fee Pool, LP, SSL, Full Precision, and More - page 53. (Read 379087 times)

projects like bithopper are very valuable because they bring bad stuff that others have been doing for a long time to the surface.

those that hop earn more, the others earn less - yep, stealing is an adequate term. Still I consider it the pool operators' duty to prevent it.

+1

Damn. Just when I was about to bring my workers/miners back to BTC Guild I see this. I will wait until something is done to prevent pool hopping on BTC Guild. Basically they are stealing from other miners by doing this, IMO.

Delayed stats needs to be implemented.

quote from the bithopper pool hopping tool thread:

How did you get into my house to find my miner control switch!

Update on the idles earlier today:  Host has modified the DDoS filtering to allow a higher packet flow before it trips on our mining server's IP.  The problem seems to have stemmed from when all 4 pools triggered a long poll within 1-2 seconds (remember that bitcoind = p2p network, and has to write to disk when a new block is found, causing minor variations in each bitcoind knowing the block chain has moved).

When all 4 subservers triggered the LP within about 1 second of each other, it launched out the new information to all miners at once.  The server is averaging about 3.5k workers right now.  Some workers are actually 2-10 miner instances, some have even more for the people who setup computers at their office to mine while idle.  Each one has its own long poll connection, and its own work queue.  The LP pushes the new work to everybody, and people re-established connections.  Many miners will request at least one additional piece of work at the same time.  This is on top of the usual getwork/share submission traffic.

The end result was a rare chance of the server triggering the DDoS filter which adapts to the traffic flooding in.  Those who were around for the old US West know that this can get much worse with how frequently miners try to reconnect when a connection is rejected.  This is why some people were still mining happily and others were disconnected.  The DDoS filter knew certain connections were "good" because they weren't spamming for connections.  The people that got disconnected however were repeatedly hitting the server, and the filter was keeping them locked out during the "attack".

I think I've found the problem.

http://i.imgur.com/neYaa.jpg

that was brutal.. glad it is over.

and then the pool scores a couple minute block to cut that 4 hour in half to a 2 hour :-)

They just inverted it to mess with all of our heads!

I've been pressing my button to toggle the luck switch but I swear it's not working.  I guess those guys didn't install the switch properly!  I'll have to drive there myself to flip it >_<

I have my turned to 99 

we need this almost 3 hour block solved! someone turn the knob to 11!

Looks like the miners are back at 100% capacity now. I will update if I see any more changes. Thanks.

The problem is somewhere in the ISP's network based on traceroute information.  The traceroute dies before it even reaches the server.  It is possible that US West has enough IPs pointed at it that the long poll is causing enough packets to flood in/out in a very short timespan and its tripping the DDoS filtering.  Or it could simply be an unrelated hardware issue at the ISP that needs fixing.  Will know more once I get a response.

I know for the miners out there it sucks to see these dips of efficiency due to idles (luckily not too long), but the good news is that this time the problem is not in server hardware or software configuration.  If this is an accidental trigger of the DDoS filters,  it may be as simple as the ISP whitelisting our IP from the DDoS filters unless we ask for it to be turned on.

Yeah there's definitely something wrong, I'm mining at about 50% capacity on US West.

Unfortunately I can't provide diagnostic information as I'm not anywhere near the miners at the moment.

Just forwarded a whole set of traceroutes to the host for US West.

It will not really matter. Plus within the next couple of weeks there will be a server just like the West one for Central/East. I use the latest version of diablo miner and I connect to both US East and West just in case one has some obscure problem.

If you can test both, then mine at both for a 24 hour period and see what works best for you. But if you want me to pick one for you, I say mine on... us central.

Seems to be better now.

Only packet loss for me now is .9% @ 69.42.216.173

EDIT: Now zero packet loss all the way down.

mtr uswest.btcguild.com aka 69.42.216.173

   .2% packet loss @ aliix-gw.ip4.tinet.net
11.7% packet loss @ aliix.10ge5-1.cr1.lax3.awknet.com
99.2% packet loss @ 69.42.216.173

Updated