Author

Topic: [CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers - page 378. (Read 903150 times)

legendary
Activity: 1792
Merit: 1047
I have just restarted the Stratum beta pool, enabling the new dynamic difficulty adjustment.  The new system should drastically reduce overhead for large mining farms.

The target rates for miners are between 1 share per 3-10 seconds.  If a miner goes beyond 1 share per 3 seconds (during a 5 minute window), that miner's difficulty is doubled.  If a miner averages less than 1 share per 10 seconds (in a 5 minute window), it will be halved.  A "miner" is defined as a connection to the pool, not an individual worker.  In the case of very quick miners, there are shorter time frames (as small as 10 seconds) used for difficulty adjustments, but these require bursts of speed that could not be explained as simply lucky.

The target share rates are still extremely fast, meaning variance should not be adversely affected by this new change.  The only issue you may run into with large farms is the per-worker speed (on the BTC Guild website) may vary heavily.  However, your total mining speed should stay very close to your actual speed.


EDIT/UPDATE:  Another quick restart.  The pool now makes sure to send difficulty=1 on a new connection, so a disconnect/reconnect (pool restart for example) scenario doesn't have the miner submitting high diff shares and only getting credit for diff=1.

Now since Dynamic Difficulty adjustment went live my workers keep getting disconnected/reconnect and only do about 10 or so tasks and then randomly jump to next pool in list.
legendary
Activity: 1750
Merit: 1007
I have just restarted the Stratum beta pool, enabling the new dynamic difficulty adjustment.  The new system should drastically reduce overhead for large mining farms.

The target rates for miners are between 1 share per 3-10 seconds.  If a miner goes beyond 1 share per 3 seconds (during a 5 minute window), that miner's difficulty is doubled.  If a miner averages less than 1 share per 10 seconds (in a 5 minute window), it will be halved.  A "miner" is defined as a connection to the pool, not an individual worker.  In the case of very quick miners, there are shorter time frames (as small as 10 seconds) used for difficulty adjustments, but these require bursts of speed that could not be explained as simply lucky.

The target share rates are still extremely fast, meaning variance should not be adversely affected by this new change.  The only issue you may run into with large farms is the per-worker speed (on the BTC Guild website) may vary heavily.  However, your total mining speed should stay very close to your actual speed.


EDIT/UPDATE:  Another quick restart.  The pool now makes sure to send difficulty=1 on a new connection, so a disconnect/reconnect (pool restart for example) scenario doesn't have the miner submitting high diff shares and only getting credit for diff=1.
hero member
Activity: 497
Merit: 500
legendary
Activity: 2156
Merit: 1072
Crypto is the separation of Power and State.
Dynamic difficulty is still planned to go live today, just working out a few issues with it.

Will dynamic difficulty affect the optimum intensity/threads settings on cgminer?
hero member
Activity: 626
Merit: 500
Mining since May 2011.
Do you have guys python-dev installed?

Ran out of space on the Pi trying to install the necessary packages.  Shocked

Followed your instructions from here on another Debian rig and it's working.  Cool
https://github.com/slush0/stratum-mining-proxy
Thanks!
legendary
Activity: 1750
Merit: 1007
Stratum payments have been pushed to main accounts once again.

Dynamic difficulty is still planned to go live today, just working out a few issues with it.
legendary
Activity: 1386
Merit: 1097
Do you have guys python-dev installed?
hero member
Activity: 626
Merit: 500
Mining since May 2011.
legendary
Activity: 3583
Merit: 1094
Think for yourself
When connecting with poclbm, make sure you type the address as:   stratum://[worker_name]:[email protected]:9332

If you use http:// instead of stratum://, it won't work.

That's what I did.  I copied, pasted and edited that line from your earlier post.  After it failed I did try the http://[worker_name]:[email protected]:8332 to verify that poclbm would work with the normal protocol and it it did.
Sam


Are you positive you have the most recent poclbm?  I just tested the EXE version again, and it connected right away with:  poclbm.exe -d0 stratum://eleuthria_fpga:[email protected]:9332

I tried it with yesterday's build and then with today's build.  Got the same error's on both.  I would say something is wrong with my setup but, it works fine with http to btcguild.com.  Dunno.
Thanks,
Sam

Edit: I just tried it with your account and it worked.  So I looked at my command line again and changed the upper case characters in my worker name to lower case and now it is working.
Thanks,
Sam
legendary
Activity: 1750
Merit: 1007
When connecting with poclbm, make sure you type the address as:   stratum://[worker_name]:[email protected]:9332

If you use http:// instead of stratum://, it won't work.

That's what I did.  I copied, pasted and edited that line from your earlier post.  After it failed I did try the http://[worker_name]:[email protected]:8332 to verify that poclbm would work with the normal protocol and it it did.
Sam


Are you positive you have the most recent poclbm?  I just tested the EXE version again, and it connected right away with:  poclbm.exe -d0 stratum://eleuthria_fpga:[email protected]:9332
legendary
Activity: 1428
Merit: 1000
I'm thinking ,
can the proxy estimate hashrate when pool enable dynamic difficulty.

yes,
but it is more complex as the proxy has to track the origin of each submitted share
good proxies already do this (eg bithopper did it - dont know if its still in there though)
legendary
Activity: 1386
Merit: 1097
I'm thinking ,
can the proxy estimate hashrate when pool enable dynamic difficulty.

Yes, miner or even proxy still can calculate hashrate estimation. Dynamic difficulty don't change anything about this. Currently it's not supported by the proxy and I'm not planning to add this to keep stuff as easy as possible, but miners will keep showing hashrate even with dynamic targets provided by server.
member
Activity: 76
Merit: 10
I'm thinking ,
can the proxy estimate hashrate when pool enable dynamic difficulty.
legendary
Activity: 3583
Merit: 1094
Think for yourself
Code:
stratum.btcguild.com:9332 18/09/2012 20:39:42, IO errors - 2, tolerance 2

stratum.btcguild.com:9332 18/09/2012 20:39:42, [Errno 9] Bad file descriptor

stratum.btcguild.com:9332 18/09/2012 20:39:45, IO errors - 3, tolerance 2

stratum.btcguild.com:9332 18/09/2012 20:39:45, No more backup pools left. Using
primary and starting over.

stratum.btcguild.com:9332 18/09/2012 20:39:45, Setting server (os2sam_CGMiner @
stratum.btcguild.com:9332)

stratum.btcguild.com:9332 [262.457 MH/s (~0 MH/s)] [Rej: 0/0 (0.00%)]

stratum.btcguild.com:9332 [262.457 MH/s (~0 MH/s)] [Rej: 0/0 (0.00%)]

what's that? (can proxy estimate hashrate ?) why I don't have it?

That's not the proxy.  That's trying to use poclbm directly since it now supports stratum.
Sam
legendary
Activity: 3583
Merit: 1094
Think for yourself
When connecting with poclbm, make sure you type the address as:   stratum://[worker_name]:[email protected]:9332

If you use http:// instead of stratum://, it won't work.

That's what I did.  I copied, pasted and edited that line from your earlier post.  After it failed I did try the http://[worker_name]:[email protected]:8332 to verify that poclbm would work with the normal protocol and it it did.
Sam
member
Activity: 76
Merit: 10
Code:
stratum.btcguild.com:9332 18/09/2012 20:39:42, IO errors - 2, tolerance 2

stratum.btcguild.com:9332 18/09/2012 20:39:42, [Errno 9] Bad file descriptor

stratum.btcguild.com:9332 18/09/2012 20:39:45, IO errors - 3, tolerance 2

stratum.btcguild.com:9332 18/09/2012 20:39:45, No more backup pools left. Using
primary and starting over.

stratum.btcguild.com:9332 18/09/2012 20:39:45, Setting server (os2sam_CGMiner @
stratum.btcguild.com:9332)

stratum.btcguild.com:9332 [262.457 MH/s (~0 MH/s)] [Rej: 0/0 (0.00%)]

stratum.btcguild.com:9332 [262.457 MH/s (~0 MH/s)] [Rej: 0/0 (0.00%)]

what's that? (can proxy estimate hashrate ?) why I don't have it?
hero member
Activity: 497
Merit: 500
legendary
Activity: 1750
Merit: 1007
I will be pushing forward an update much later today (~12 hours) which implements dynamic difficulty adjustments for miners.  There have been three big obstacles in implementing this so far:

1) Adjusting it quickly for very fast miners so they aren't spending many minutes at Difficulty=1.
2) Allowing the difficulty to adjust down when a miner slows down (machines changing pools/crashing).
2) Finding a way to adjust it that doesn't open up holes to exploiting the system (withhold high diff shares for when difficulty is increased for higher reward).


I believe I have found a way to handle all 3 of these scenarios.  As stated previously, the target rate of share submissions for a user is 1 share per 5 seconds.  This frequency keeps personal variance very low, to the point where a 24 hour window will not see any noticeable fluctuations.


Difficulty adjustment is the last step for the "beta" stage of the pool.  After the update, I will push out the Wednesday stratum payments.  If nothing is breaking between Wednesday and Friday, I will begin working on making the Stratum pool part of the main frontend, and hopefully complete that transition Sunday with a final beta payment.
legendary
Activity: 1750
Merit: 1007
legendary
Activity: 1750
Merit: 1007
When connecting with poclbm, make sure you type the address as:   stratum://[worker_name]:[email protected]:9332

If you use http:// instead of stratum://, it won't work.
Jump to: