Search content
Sort by
Showing 6 of 6 results by Rudycoin
Re: BTC Guild - 0% Fees, Long polling, SSL, JSON API, and more [~850 gH/sec]
API is currently polling some stats incorrectly. This should be fixed early tomorrow morning.
It appears that my shares are not rising at all, they seem to be stuck at 456, I hope this is what you are fixing because it has really effected my payout.Re: BTC Guild - 0% Fee Pool, Long polling, JSON API, invalid insurance [~275 gH/sec]
No access to RPC or website... would that mean server transition is in progress, or am I having some sort of issue of my own?
Good job on the pool, anyhow, considering the fast growth and everything. I'll be sure to bump up my donation percentage a bit when I can reach the site again.
Good job on the pool, anyhow, considering the fast growth and everything. I'll be sure to bump up my donation percentage a bit when I can reach the site again.
X2 on the issues.
Last hop is gone:
10 93 ms 94 ms 92 ms pos-1-13-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.85.162]
11 93 ms 96 ms 94 ms pos-0-6-0-0-ar03.sacramento.ca.sacra.comcast.net [68.86.93.218]
12 97 ms 99 ms 102 ms te-0-4-0-4-ar03.fresno.ca.fresno.comcast.net [68.85.196.49]
13 106 ms 105 ms 109 ms te-4-2-ar02.fresno.ca.fresno.comcast.net [68.85.196.22]
14 102 ms 105 ms 99 ms te-8-3-ar01.fresno.ca.fresno.comcast.net [68.87.200.1]
15 100 ms 98 ms 102 ms te-9-1-ur01.shaw.ca.fresno.comcast.net [68.87.200.26]
16 117 ms 112 ms 115 ms te-17-10-cdn03.shaw.ca.fresno.comcast.net [68.85.120.102]
17 * * * Request timed out.
Re: BTC Guild - 0% Fee Pool, Long polling, JSON API, invalid insurance [~275 gH/sec]
I have just started mining with you yesterday. I noticed that after I added 2x more 5850's to my system that the Worker Speed reported on your site is now not consistent (about 50-60%) with what is displayed when running Diablo Miner. Just wondering why this is happening, or if my Miner needs tweaking.
Diablo Displays ~ 866 mH/sec and your site hovers around 410-420 mH/sec
the command line is using -v 2 -w 128 as this results in the highest speed.
could the -w 128 be causing this?
Just wondering if the issue is me or the site?
Diablo Displays ~ 866 mH/sec and your site hovers around 410-420 mH/sec
the command line is using -v 2 -w 128 as this results in the highest speed.
could the -w 128 be causing this?
Just wondering if the issue is me or the site?
As has been posted for the last few days, the server needs to be relocated to a dedicated host, which is lined up but not yet ready.
The amount on the site is NEVER the same as your miner, it's a 15 minute average. Right now it will likely be less due to occasional miner idles that are being caused by the current volume of workers on the server. This is the reason new registrations were closed, the current server cannot handle the load (we grew over 100 GH/sec in 4 days).
Ahh, ok. I figured the statistics would not match EXACTLY but within 100 mH/sec, this is way too far off for something not to be up.
The miner is now up for over 12 H and has been lingering around 866 mH/sec for most of the session, so I would expect the 15 minute moving average to be somewhat close.
When do you anticipate the relocation to happen? Sounds like some work, I hate moving stuff like that at work.
Thanks for your reply.
Re: BTC Guild - 0% Fee Pool, Long polling, JSON API, invalid insurance [~275 gH/sec]
I have just started mining with you yesterday. I noticed that after I added 2x more 5850's to my system that the Worker Speed reported on your site is now not consistent (about 50-60%) with what is displayed when running Diablo Miner. Just wondering why this is happening, or if my Miner needs tweaking.
Diablo Displays ~ 866 mH/sec and your site hovers around 410-420 mH/sec
the command line is using -v 2 -w 128 as this results in the highest speed.
could the -w 128 be causing this?
Just wondering if the issue is me or the site?
Diablo Displays ~ 866 mH/sec and your site hovers around 410-420 mH/sec
the command line is using -v 2 -w 128 as this results in the highest speed.
could the -w 128 be causing this?
Just wondering if the issue is me or the site?