[~1000 GH/sec] BTC Guild - 0% Fee Pool, LP, SSL, Full Precision, and More

[hugolp]

This seems to be a great pool.

Ive been mining it more and more since I started with it a few weeks ago to the point its now more or less the pool I devote all my mining time too.

Their tekin' urr pools!!!

[1714022209]

1714022209

[1714022209]

1714022209

[1714022209]

1714022209

[ElectroGeek007]

Holy... 24-Hour Luck: +58%! Nice.

[mike85123]

Really starting to miss the realtime stats 

[sirky]

Really starting to miss the realtime stats 

Why?

[dime]

I've been mining from both uswest and uscentral for the past 48 hours and I'm getting a lot of disconnects:
5830:
[159.05 Mhash/sec] [4635 Accepted] [386 Rejected] [RPC (+LP)]
[159.06 Mhash/sec] [4427 Accepted] [389 Rejected] [RPC (+LP)]

6850:
[124.81 Mhash/sec] [1122 Accepted] [136 Rejected] [RPC (+LP)]
[124.82 Mhash/sec] [1093 Accepted] [157 Rejected] [RPC (+LP)]

6850:
[120.70 Mhash/sec] [961 Accepted] [155 Rejected] [RPC (+LP)]
[120.69 Mhash/sec] [977 Accepted] [144 Rejected] [RPC (+LP)]

5770:
[109.04 Mhash/sec] [331 Accepted] [66 Rejected] [RPC (+LP)]
[109.71 Mhash/sec] [333 Accepted] [71 Rejected] [RPC (+LP)]

5770:
[109.46 Mhash/sec] [297 Accepted] [66 Rejected] [RPC (+LP)]
[109.41 Mhash/sec] [296 Accepted] [64 Rejected] [RPC (+LP)]

I seem to get different %'s for different cards/computers on the same network.

Pretty much all of those rejected is from something like this:
[31/07/2011 15:37:19] Result: 82817999 accepted
[31/07/2011 15:38:41] Disconnected from server
[31/07/2011 15:38:41] Result: a35d8225 rejected
[31/07/2011 15:38:44] Connected to server
[31/07/2011 15:39:09] Result: 41217ec4 accepted
[31/07/2011 15:40:42] Disconnected from server
[31/07/2011 15:40:42] Result: d7afebf3 rejected
[31/07/2011 15:40:54] Connected to server
[31/07/2011 15:40:54] Result: 3ea5ff08 accepted

It happens on and off.. My internet connection is rock steady as I stay connected to my company vpn 24/7 and I basically never get d/c from slush's pool when I mine there.

Any troubleshooting ideas?

[Dargo]

This seems to be a great pool.

Ive been mining it more and more since I started with it a few weeks ago to the point its now more or less the pool I devote all my mining time too.

+1 Every time I move to another pool, I seem to end up coming back here pretty quickly.

[mike85123]

Really starting to miss the realtime stats 

Why?

I fully support the delay to bounce out the hoppers, I just dislike being in the dark about how long the current round is taking... Have yet to fully understand the "estimated shares this round" and a few others.  BTCG is much more transparent than deepbit though.

[sirky]

Really starting to miss the realtime stats 

Why?

I fully support the delay to bounce out the hoppers, I just dislike being in the dark about how long the current round is taking... Have yet to fully understand the "estimated shares this round" and a few others.  BTCG is much more transparent than deepbit though.

I understand that information is good, and it is just nice to know. But with a proportional pool, you simply cannot give out live stats. Even with a one hour delay, it isn't completely hopper proof, only hopper resilient. The only way a proportional pool could be hopper proof is to have the delay be longer than any round could ever legitimately be (for guild, something like 8 or 12 hours). And even then there is some longpolling nonsense that can be done to try and guess if a block has been solved by Guild or someone else.

The estimated shares this round are the number of shares that the round would approximately be if the block was not found in the last hour.

[mike85123]

@eleuthria,

Any chance to color code a row on the worker table to red if they haven't submitted a share in x minutes (something around 5 mins)? Anyone else think that would be a good feature?

[jayfitt]

I am glad that some people see their income has gone up (previous post a while ago on this page)...but in my case,
while my speeds are pretty consistent on two of my miners at 385 Mh/s and 285 Mh/s, respectively, btcguild often records them much much lower...my income has actually gone DOWN today...from average 0.0214 for 1.183 Gh/s (both 96 hr averages) to 0.0173 for 1.183 Gh/s today.

Why?

Difficulty increased today, maybe that's why?

[eleuthria]

I am glad that some people see their income has gone up (previous post a while ago on this page)...but in my case,
while my speeds are pretty consistent on two of my miners at 385 Mh/s and 285 Mh/s, respectively, btcguild often records them much much lower...my income has actually gone DOWN today...from average 0.0214 for 1.183 Gh/s (both 96 hr averages) to 0.0173 for 1.183 Gh/s today.

Why?

Those look like per block averages?  Pool speed has been steadily increasing, meaning we make more blocks, but you make less per block.

[eleuthria]

It happens on and off.. My internet connection is rock steady as I stay connected to my company vpn 24/7 and I basically never get d/c from slush's pool when I mine there.

Any troubleshooting ideas?

All I can suggest is switching servers from Central/West to the other, and/or upgrading your miner.

[bodhipraxis]

I have exactly the same experience. My rewards are off 70% from yesterday. Due to the temperature today, I left one machine off, and ran two linux boxes, which combine usually for 820 Mh/s. and under last difficulty, from 0.010 to 0.015 per round. They are SEVERELY off today, with long disconnects!!!

From school today I checked the BTC Guild webpage. FREQUENTLY, my third worker (second box of two today) was at 80 - 90 Mh/s.  This is a steady worker, 280 Mh/s and goes all day, on a very steady internet connection. That means I have same experience as the other fellow -- LONG LONG timeouts.

I just got home. Yep-- 0 Mhashes/sec.  Scrolled up -- yep, this has been happening for the last EIGHT hours.

What is going on, Eleuthira??

[bodhipraxis]

I am glad that some people see their income has gone up (previous post a while ago on this page)...but in my case,
while my speeds are pretty consistent on two of my miners at 385 Mh/s and 285 Mh/s, respectively, btcguild often records them much much lower...my income has actually gone DOWN today...from average 0.0214 for 1.183 Gh/s (both 96 hr averages) to 0.0173 for 1.183 Gh/s today.

Why?

Difficulty increased today, maybe that's why?

NO.  The servers are idling miners today. THAT is why. The drop is TOO severe.

[bodhipraxis]

I switched one of my miners to uscentral, and shares are being accepted again -- the reason my shares dropped today was NOT due to difficulty increase, but to the fact that uswest was only accepting shares from one of my miners regularly (they are all NAt'd behind one IP).
Okay, okay, so I need to use a proxy, right? I just have never experienced this kind of drastic timeout with BTC for quite a while.

[TheMalon]

NO.  The servers are idling miners today. THAT is why. The drop is TOO severe.

That usually means connection problem (big latency).
Looking to your signature (2 workers = 600+Mhs) make me think you have 2 powerful miners ... so you need o good network latency or configure better your miners (try to get more work doing more getwork requests and buffer them).

Ciao

[TheMalon]

I switched one of my miners to uscentral, and shares are being accepted again -- the reason my shares dropped today was NOT due to difficulty increase, but to the fact that uswest was only accepting shares from one of my miners regularly (they are all NAt'd behind one IP).
Okay, okay, so I need to use a proxy, right? I just have never experienced this kind of drastic timeout with BTC for quite a while.

If they are NAT'ed ... you DON'T need a proxy!

[TheMalon]

NO.  The servers are idling miners today. THAT is why. The drop is TOO severe.

That usually means connection problem (big latency).
Looking to your signature (2 workers = 600+Mhs) make me think you have 2 powerful miners ... so you need o good network latency or configure better your miners (try to get more work doing more getwork requests and buffer them).

Ciao

NVM ... Just looked at poolpush server code ... it seems that you can't buffer requests (will fail the submission of the result).

[bodhipraxis]

NO.  The servers are idling miners today. THAT is why. The drop is TOO severe.

That usually means connection problem (big latency).
Looking to your signature (2 workers = 600+Mhs) make me think you have 2 powerful miners ... so you need o good network latency or configure better your miners (try to get more work doing more getwork requests and buffer them).

Ciao

so what would you suggest, other than the following (I am using Phoenix 1.50):

${HOMEDIR}/phoenix-1.50/phoenix.py -u http://${MINERUSER}:${MINERPASS}@${$MINERSERV} -q 3 -k phatk VECTORS BFI_INT AGGRESSION=12 WORKSIZE=128 DEVICE=${1}

where $MINERSERV is either uswest or uscentral.

Both miners on Xubuntu boxen, one is catalyst 11.5, the other is 11.6; both use APP SDK 2.4. (that shouldn't affect the behavior that is occurring today with BTCGuild)

[bodhipraxis]

BTW, another interesting thing is that weird network behavior with the mining server correlates well with freezes of the card (it is a 5830). IE long periods at Zero increase the likelihood that the card will freeze the OS.