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

[ensign_lee]

Hey,

Are any of y'all getting a disproportionate amount of stale shares? I only got 1 stale shared out of like a thousand at Slush's, but I seem to be getting one every 50-75 shares here. :?

Didn't seem to change when I switched from a 5770 to a 5870 either. :/

Am I the only one experiencing this?

[eleuthria]

Hey,

Are any of y'all getting a disproportionate amount of stale shares? I only got 1 stale shared out of like a thousand at Slush's, but I seem to be getting one every 50-75 shares here. :?

Didn't seem to change when I switched from a 5770 to a 5870 either. :/

Am I the only one experiencing this?

Is that stale count from the beginning of time, or since the pool came back up from maintenance about 9 hours ago?  I'm running at a 0.1% stale rate, and a few people in the IRC channel have reported similar 0.1-0.4% stale rates, normally coming when a share is submitted immediately as a long poll is being received.

Send me a PM with your worker name, and which mining software you use.  I can take a look at your recent submissions to find out why they're being rejected.

[jme621]

just joined, thanks.

EDIT: ok maybe i didnt, do i use the settings from page 13 or post #1 if i am using the gui miner?

Using the GUI miner, do this:

Server: Other
Host: btcguild.com
Username: (your worker name)
Password: (your worker password)
Port: 8332
Device: (your GPU, not CPU)

Thank you 

[pist0la]

Joined this pool. around 310Mhash/sec currently, adding another 300-340 in a couple hours.

[Muhahahahaz]

Pool down!

[REF]

pool is down, any idea when its coming back up?

[grndzero]

Site and mining are down for me.

[REF]

Does anyone know what is wrong?

[Elgost]

Its strange that the pool goes down without any warning...
The hardware broke?

[grndzero]

Its strange that the pool goes down without any warning...
The hardware broke?

Maybe he blew a breaker? lol

[PiGames]

No update?
Seems to have been down for ~4hrs or so.
Hopefully it's nothing 'serious'.

[Basiley]

seems http://www.btcguild.com/ really down  [resolved as 74.95.106.214].
probably some problems. technical or moral.
also quite familar for comcast [tracing was broke on ten(in chain ) comcast nodes/gates]is to take down connection services for bogus reasons or without reasons for all[maybe after class-act lawsuit something change].

[Muhahahahaz]

It's back!

[eleuthria]

As is the standard, the server decided to wait until a few hours after I was asleep, but a few hours before I would wake up to die.  I did not have time before work to diagnose what happened, all I know is that the server was not responding to connections, even SSH from the internal network.  I did a hard boot and restarted the server processes.  I will attempt to diagnose the problem with what log files are available when I return home.

[grndzero]

As is the standard, the server decided to wait until a few hours after I was asleep, but a few hours before I would wake up to die.  I did not have time before work to diagnose what happened, all I know is that the server was not responding to connections, even SSH from the internal network.  I did a hard boot and restarted the server processes.

Last I saw before it went down it was in the 90 Gh/s range. My Estimated Rewards correlated to that. Database and/or bitcoind logging overload? Not sure why it would lock up the rest of the system unless there was a memory leak introduced somewhere in the upgrades or temp/log files were eating up a lot of hard drive space.

New hardware is always awesome but almost almost always causes it's own problems.

[Elgost]

New hardware is always awesome but almost always causes it's own problems.

So true

[Nythain]

Shameless bump to keep us on the front page

[REF]

The counter for m/hash on your website seems to be off a bit for my workers. worker1 on my PC is at anywhere from 520-590 m/hash, but on the site it shows that its between 200-590 m/hash, and consistently says its at 350 m/hash or below.

[grndzero]

The counter for m/hash on your website seems to be off a bit for my workers. worker1 on my PC is at anywhere from 520-590 m/hash, but on the site it shows that its between 200-590 m/hash, and consistently says its at 350 m/hash or below.

That's because your workers don't return work at a consistent rate. Look at the column that says Last Share. Some getworks take longer than others to process, so the math is constantly changing trying to calculate it. Once you've been running for a while your Total Worker Speed should be roughly correct and that's all that matters.

[BitcoinsWallet]

Signed up and mining from now