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

Fixed the problem with payout processing.

I've also had quite a few emails regarding the new stats "Last Block Awarded" and "Shares Since Last".

Last Block Awarded is just as it sounds.  It's how long since a block was announced and the rewards were allocated to accounts.  Everytime that timer resets, you will have new confirmed/unconfirmed rewards (assuming you participated in that block).

"Shares Since Last" is a compromise.  Many people were upset that "Round Shares" was removed.  The increasing counter provided some sign that the server as a whole was continuing to accumulate shares towards the next block.

The value of Shares Since Last will be equal to:  The number of shares since the last block announcement, plus one hour.  So if a block was announced 45 minutes ago, Shares Since Last will contain 1 hour and 45 minutes of shares.  There may be any number of unannounced blocks that are waiting to be announced (solved within the last hour).  It is possible there are no blocks in that number as well.

Not a big issue unless you've never cashed out and is storing huge amounts on your BTC Guild account

seems to be fixed now, thanks.

+1! Very nice!

knowing our luck BTC will spike to 30 bucks and then go down as soon as it is fixed ;-)

same here hope its fixed soon

i am hoping this will stop the ddos.

"Request Payout" now gives me An error occurred while processing your payout, please try again..

Anyone else having problems with payouts or is it just me? :/

Could you provide the server address here or on the site incase someone were to be doing this, and wanted to proactively move to that server

E:,  that sounds like a good compromise for the cpu miners (no long polling)   NICE JOB>

Always nice to see a proactive server admin

I've started to single out suspect accounts which are either being used by a lot of IPs, or showing a large number getworks with low return rates/speed (likely to be a very large CPU mining operation).

While CPU mining is not banned from BTC Guild, they are discouraged when used in large numbers.  They are ineffective, slow, and anybody running them is likely doing so either behind the owner's back (computer lab/client computers of an IT company), or by misinforming the owner's ("They're on 24/7 anyway").

There is absolutely no situation I can find where it is cost effective for somebody to be running a CPU server farm for mining.  Somebody is going to eat that bill, and I highly doubt its the person running them.  By running these huge numbers of CPU miners, you are negatively impacting the rest of the pool.  Each CPU miner is consuming server resources similar to a GPU miner.  Long poll sessions are a fixed cost for the pool regardless of the miner speed.  Additionally, most of these CPU miners are asking for work every 5 or 10 seconds, even though they take many minutes to send something back.

If your account gets singled out, you will see a large warning on the My Account page directing you to a special server address which has long polling disabled.  This special server was put in place to keep the primary servers healthy and running stable.

The 500 GH/s surge was inaccurate.  The speed is calculated by share submissions in the last 15 minutes.  Somebody tried to game the system by submitting the same share from a large number of miners all at once.  Obviously the pool returned them as invalid, but invalids still get included in the share submissions for the last 15 minutes, causing the speed to show a huge sipke.


I applied a fix to the worker stats caching which should eliminate the '0 speed' glitch.

This is correct.

didn't it seem like ~2000 gh/s was a sweet spot for a pool? or maybe it was just me.
but yes.. it looks like delayed stats is not hurting the pool as it is still growing. stability
seems to be a key ingredient for that.

I am new too, but I think I know the answer to this one.

when you see a new block being worked on, you dont know what pool, or solo person found the last block, so you dont know which pool to jump on to.

Jim

Question about pool hopping and the 1 hour delay...

It's too bad pool hopping caused us to lose the ability to get a more real-time look at what's going on....anyhow, am new to this but it seems that you could easily see when a block ends simply by watching the log console output when you get a new block?  Am I missing something?  Just wondering if this is actually effective or we're just hurting the honest folks.

PS: I don't 'hop' to abuse the system but I have been in and out of a few pools as I try to figure all this stuff out and which site I like the best.  So far I do like the look & feel of BTC Guild's website the best for what it's worth.

Whoa, just jumped 500+ Ghash since my last refresh like 15 minutes ago?

the display showing 0 one load, then proper the next does not seam like a big deal...

I am more concerned that my share just dropped about 20%.  from .135 to about .11

must be the increase in giga... 
7,534 workers at 2866.66 GH/s

this was at 2200 last I looked

I've been noticing this as well. All zero values but a refresh will get the expected values displayed again.