Topic: [~1000 GH/sec] BTC Guild - 0% Fee Pool, LP, SSL, Full Precision, and More - page 101. (Read 379078 times)
June 12, 2011, 10:03:11 PM
The thing is, and I've said this about 50 times in various threads around these boards, you can't make any claims about a single event.
June 12, 2011, 09:39:12 PM
Is there currently a reporting problem? I see this:
9,553 workers at 1,536.46 GH/s
Round Time 3:36:20 Round Shares 4577435
Statistically speaking this is extremely improbable. Is all the server shuffling creating problems for the website such that it doesn't really know when a block was found? Or are we really just winning the anti-lottery?
9,553 workers at 1,536.46 GH/s
Round Time 3:36:20 Round Shares 4577435
Statistically speaking this is extremely improbable. Is all the server shuffling creating problems for the website such that it doesn't really know when a block was found? Or are we really just winning the anti-lottery?
No, it's actually not that improbable. Just means the pool is unlucky, other pools are solving the block before we can.
As I understand it other pools solving blocks doesn't affect our chances of solving a block at all, it is random chance when we hit one. Having 1500GH/s just means we buy 1.5 trillion lottery tickets every second. Sure we start using a new block header for hashes every time anyone solves a block, but that doesn't change the odds. According to my limited understanding we have a 95% chance of finding a block within 1.5 hours at that hash rate. A 2 hour round is an anomaly, a 3.5 hour round seems damn near impossible. Not actually impossible, but so unlikely as to make me wonder if something else is going on. It is certainly possible I'm misunderstanding things, I am no statistical genius. Please educate me.
June 12, 2011, 09:37:13 PM
I appreciate all of your hard work, eleuthria. This has been a great pool, despite the growing pains; the growing hash rate reflects that.
I'm increasing my donations from 2.5% to 3%, to help pay for all of those new servers and maybe a few pots of coffee.
I'm increasing my donations from 2.5% to 3%, to help pay for all of those new servers and maybe a few pots of coffee.
June 12, 2011, 09:24:21 PM
Is there currently a reporting problem? I see this:
9,553 workers at 1,536.46 GH/s
Round Time 3:36:20 Round Shares 4577435
Statistically speaking this is extremely improbable. Is all the server shuffling creating problems for the website such that it doesn't really know when a block was found? Or are we really just winning the anti-lottery?
9,553 workers at 1,536.46 GH/s
Round Time 3:36:20 Round Shares 4577435
Statistically speaking this is extremely improbable. Is all the server shuffling creating problems for the website such that it doesn't really know when a block was found? Or are we really just winning the anti-lottery?
No, it's actually not that improbable. Just means the pool is unlucky, other pools are solving the block before we can.
June 12, 2011, 09:04:28 PM
Is there currently a reporting problem? I see this:
9,553 workers at 1,536.46 GH/s
Round Time 3:36:20 Round Shares 4577435
Statistically speaking this is extremely improbable. Is all the server shuffling creating problems for the website such that it doesn't really know when a block was found? Or are we really just winning the anti-lottery?
9,553 workers at 1,536.46 GH/s
Round Time 3:36:20 Round Shares 4577435
Statistically speaking this is extremely improbable. Is all the server shuffling creating problems for the website such that it doesn't really know when a block was found? Or are we really just winning the anti-lottery?
June 12, 2011, 08:41:59 PM
Can anyone give me some advice on getting my stale rate down. Over a 24 hour period, running 13 gpu's on BTC Guild, I am getting a 5.2% stale rate according to the stats on the my account page. With deepbit I was getting around 3% and with slush I was getting around 4%. None of these numbers are good when I see people saying they get less that 1% stale rate.
Any ideas? I am running phoenix using the phatk kernel. Below is my command line:
phoenix.exe -u http://XXXXXXXX:[email protected]:8332/ -k phatk DEVICE=1 VECTORS BFI_INT FASTLOOP=false WORKSIZE=256 AGGRESSION=13
Thanks.
Any ideas? I am running phoenix using the phatk kernel. Below is my command line:
phoenix.exe -u http://XXXXXXXX:[email protected]:8332/ -k phatk DEVICE=1 VECTORS BFI_INT FASTLOOP=false WORKSIZE=256 AGGRESSION=13
Thanks.
Toning down the aggression can help. Additionally, the IRC chat has universally agreed that phoenix's stale rate is completely terrible right now, since it seems to ignore clearing out its work queue after receiving a long poll.
Pool Status Update:
US West is getting bogged down compared to the other servers. I'm working on shifting some of the frequent MySQL tasks to the slave pools to help it handle the load. Eventually the frontend will get moved to a separate server so that the pool itself on US West is not significantly affected by website load.
Which miner do you recommend to use?
June 12, 2011, 08:13:55 PM
US Central (Chicago) will hopefully be online tomorrow or the day after. Also obtaining a separate server to handle the website to get that load off of the US West pool server.
This is great news. Thanks for all your hard work.
June 12, 2011, 08:08:48 PM
US Central (Chicago) will hopefully be online tomorrow or the day after. Also obtaining a separate server to handle the website to get that load off of the US West pool server.
June 12, 2011, 02:50:12 PM
this pool seems to have bad luck as of late 
If I tabulate the average round shares for the last 2 days. It is about 33% higher than the difficulty of 567358...while on deepbit it about 10%...meaning if i were to mine on deepbit i would have got 20% more...oh well lets lope for the tide to change
If I tabulate the average round shares for the last 2 days. It is about 33% higher than the difficulty of 567358...while on deepbit it about 10%...meaning if i were to mine on deepbit i would have got 20% more...oh well lets lope for the tide to change June 12, 2011, 12:27:29 PM
I would love to see a 24hr average BTC earned under the accounts page.
I'm still hoping to get that feature in this weekend. I was sick most of the weekend, and my attention was focused on the server sync issues with the UK server. Right now I'm working on getting a lot of the computational/SQL load for the frontend to be distributed to the slave servers, to speed up the My Account/API pages, as well as help the US West server from having idles.
June 12, 2011, 11:41:24 AM
I would love to see a 24hr average BTC earned under the accounts page.
June 12, 2011, 11:02:47 AM
Can anyone give me some advice on getting my stale rate down. Over a 24 hour period, running 13 gpu's on BTC Guild, I am getting a 5.2% stale rate according to the stats on the my account page. With deepbit I was getting around 3% and with slush I was getting around 4%. None of these numbers are good when I see people saying they get less that 1% stale rate.
Any ideas? I am running phoenix using the phatk kernel. Below is my command line:
phoenix.exe -u http://XXXXXXXX:[email protected]:8332/ -k phatk DEVICE=1 VECTORS BFI_INT FASTLOOP=false WORKSIZE=256 AGGRESSION=13
Thanks.
Any ideas? I am running phoenix using the phatk kernel. Below is my command line:
phoenix.exe -u http://XXXXXXXX:[email protected]:8332/ -k phatk DEVICE=1 VECTORS BFI_INT FASTLOOP=false WORKSIZE=256 AGGRESSION=13
Thanks.
Toning down the aggression can help. Additionally, the IRC chat has universally agreed that phoenix's stale rate is completely terrible right now, since it seems to ignore clearing out its work queue after receiving a long poll.
Pool Status Update:
US West is getting bogged down compared to the other servers. I'm working on shifting some of the frequent MySQL tasks to the slave pools to help it handle the load. Eventually the frontend will get moved to a separate server so that the pool itself on US West is not significantly affected by website load.
June 12, 2011, 10:31:21 AM
Can anyone give me some advice on getting my stale rate down. Over a 24 hour period, running 13 gpu's on BTC Guild, I am getting a 5.2% stale rate according to the stats on the my account page. With deepbit I was getting around 3% and with slush I was getting around 4%. None of these numbers are good when I see people saying they get less that 1% stale rate.
Any ideas? I am running phoenix using the phatk kernel. Below is my command line:
phoenix.exe -u http://XXXXXXXX:[email protected]:8332/ -k phatk DEVICE=1 VECTORS BFI_INT FASTLOOP=false WORKSIZE=256 AGGRESSION=13
Thanks.
Any ideas? I am running phoenix using the phatk kernel. Below is my command line:
phoenix.exe -u http://XXXXXXXX:[email protected]:8332/ -k phatk DEVICE=1 VECTORS BFI_INT FASTLOOP=false WORKSIZE=256 AGGRESSION=13
Thanks.
June 12, 2011, 10:15:43 AM
Heh, I wish you had given some notice that you were going to take down the miner1.btcguild.com URL. All of my stuff was still pointed to it, and I didn't notice it was gone for about 10 hours.
I use the flex proxy, so I didn't lose any work, but I was pretty confused trying to figure out why my stuff wasn't working while the website kept counting up rounds.
Edit: fixed .org -> .com
I use the flex proxy, so I didn't lose any work, but I was pretty confused trying to figure out why my stuff wasn't working while the website kept counting up rounds.
Edit: fixed .org -> .com
I am very sorry for this lack of notice on this. I migrated our DNS servers to DNS Made Easy, and that entry was lost in the shuffle.
June 12, 2011, 09:51:37 AM
Heh, I wish you had given some notice that you were going to take down the miner1.btcguild.com URL. All of my stuff was still pointed to it, and I didn't notice it was gone for about 10 hours.
I use the flex proxy, so I didn't lose any work, but I was pretty confused trying to figure out why my stuff wasn't working while the website kept counting up rounds.
Edit: fixed .org -> .com
I use the flex proxy, so I didn't lose any work, but I was pretty confused trying to figure out why my stuff wasn't working while the website kept counting up rounds.
Edit: fixed .org -> .com
June 12, 2011, 09:41:43 AM
Thanks for handling that so quick, You Rock! 
June 12, 2011, 09:40:12 AM
Last nights rounds have now been properly calculated. Apache was locking up overnight which runs the front-end calculations. Nothing was lost at all, and thanks to all the security checks I added for server sync, all the round data is in-tact, including accurate timestamps for each block's solve time.
To keep up with my track record, the technical cause of the issue was that the pool's massive expansion (we were capped at 550-600 GH/sec as of Monday, it is now at nearly 1.5 TH/sec on Sunday) finally found something new to break. The Apache server had been modified only slightly to give the MaxClients value to the max of 256 (before adding a ServerLimit change, which I did this morning). With the pool's massive growth, and the variety of apps/widgets out there which poll the API once per minute, the limit was just too low. Luckily, the Apache side is hosted on US West, which has massive amounts of RAM and a much better processor than the slave servers, so increasing this value was not a problem.
To keep up with my track record, the technical cause of the issue was that the pool's massive expansion (we were capped at 550-600 GH/sec as of Monday, it is now at nearly 1.5 TH/sec on Sunday) finally found something new to break. The Apache server had been modified only slightly to give the MaxClients value to the max of 256 (before adding a ServerLimit change, which I did this morning). With the pool's massive growth, and the variety of apps/widgets out there which poll the API once per minute, the limit was just too low. Luckily, the Apache side is hosted on US West, which has massive amounts of RAM and a much better processor than the slave servers, so increasing this value was not a problem.
June 12, 2011, 09:28:03 AM
Round shares get reset again. I think the pool just get another block, but the web interface is not working.
June 12, 2011, 09:17:40 AM
lets hope it is solving blocks at all... doesnt look like it anymore.
June 12, 2011, 09:16:55 AM
the main page claims
9,584 workers at 1,496.59 GH/s
Round Time 4:46:03 Round Shares 611823
how is this even possible? this much shares are contributed in about 30 min at that speed...
9,584 workers at 1,496.59 GH/s
Round Time 4:46:03 Round Shares 611823
how is this even possible? this much shares are contributed in about 30 min at that speed...
Jump to: