Should we have a limit at some point? How many members are we shooting for?
I thought about having multiple groups at once, that that is kinda a pain and would suck if one group get's lucky and other does not. So I think staying to one group is best.
Topic: Sidehack stick solo pool club - page 11. (Read 27076 times)
@Phil:
Thanks, I'll adjust my Pi tonight when I get home later tonight.
Thanks, I'll adjust my Pi tonight when I get home later tonight.
I've only read back about 5 pages, so I'll ask a simple question:
Is it to late to join? I've got two sticks that are working, and would like to try my hand here. I kinda like the simple share plan that Phil laid out, but I don't want to "overflow" things.
Is it to late to join? I've got two sticks that are working, and would like to try my hand here. I kinda like the simple share plan that Phil laid out, but I don't want to "overflow" things.
you would be number 26 so your share will be 1/26
join use this:
stratum+tcp://solo.ckpool.org.3333
1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.alhstick
if you do it correctly it should show here
http://solo.ckpool.org/workers/1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.alhstick
I've only read back about 5 pages, so I'll ask a simple question:
Is it to late to join? I've got two sticks that are working, and would like to try my hand here. I kinda like the simple share plan that Phil laid out, but I don't want to "overflow" things.
Is it to late to join? I've got two sticks that are working, and would like to try my hand here. I kinda like the simple share plan that Phil laid out, but I don't want to "overflow" things.
Thanks Kano. That's helpful.
But just a clarification. Since I'm running two sticks and there's just one instance of cgminer, won't the average time to detect a disconnect effectively be cut in half?
If it really makes sense to get to a share every 5 seconds, I want to understand the effect of multiple units on the equation. Unless it makes more sense to plan for the worst case and optimize for a single unit.
Of course with a whopping total of 32 GH/s, clearly I'm not really in this to win. While optimizing is generally good advice, from a pragmatic standpoint it's unlikely that it will mean the difference between finding and not finding a block for me.
If you are mining with a single cgminer at diff D with G GHs of hardware then you'll expect, on average:But just a clarification. Since I'm running two sticks and there's just one instance of cgminer, won't the average time to detect a disconnect effectively be cut in half?
If it really makes sense to get to a share every 5 seconds, I want to understand the effect of multiple units on the equation. Unless it makes more sense to plan for the worst case and optimize for a single unit.
Of course with a whopping total of 32 GH/s, clearly I'm not really in this to win. While optimizing is generally good advice, from a pragmatic standpoint it's unlikely that it will mean the difference between finding and not finding a block for me.
1 share every (D * 2^32) / (G * 10^9) seconds
Yeah that's obvious
of course.Or to simplify it you get 1 share every ~4.3 * D / G seconds
So at G = 32, a D of 32 will mean ~4.3 seconds per share, on average.
Anyway, yes your share rate depends on your total hash rate G vs the difficulty you are using D
So if you double G and keep D the same, then yes you'll get, on average, twice as many shares.
Your miner should also show a WU value that matches that anyway (but in shares per minute)
I pointed a second stick to my club address, this one also only at 125 freq. I need to get a second hub so I can up-clock these a bit.
I might suggest getting some Y adapters for them aswell if you really want to play with them. They allow you to get much higher freq's.
I still have not had time to set up mine yet for a nice OC.
Yea, I need to grab a couple of those for sure. I've only pushed a couple of my sticks to 250, at that freq they draw about 0.9A from the hub I use (which claims 1A at each port). I'll need those Y cables to start playing in the 300 freq range.
The pool "talks" to you every 30s (at least) to give you new work.
Keeping your average share rate more active than that is advisable since you have a better chance of finding out about a disconnect sooner.
Personally I'd not put the average share rate less often than every 5s.
Remember that the same statistics apply to shares as to blocks.
A 800%+ Diff block on a pool is rare, but expected to happen 1 in every 2981 blocks.
Same for shares, you'd expect one to show up 8+ times slower than the expected value, 1 in every 2981 shares.
That's not a lot of shares ...
A simple CDF table to refer to:
So if you have it set to expect 1 share every minute, then you'd actually expect on average to have one in every 7.4 shares taking 2min (200%) or longer, and one in every 148.4 shares taking 5min (500%) or longer.
Keeping your average share rate more active than that is advisable since you have a better chance of finding out about a disconnect sooner.
Personally I'd not put the average share rate less often than every 5s.
Remember that the same statistics apply to shares as to blocks.
A 800%+ Diff block on a pool is rare, but expected to happen 1 in every 2981 blocks.
Same for shares, you'd expect one to show up 8+ times slower than the expected value, 1 in every 2981 shares.
That's not a lot of shares ...
A simple CDF table to refer to:
Code:
0.86466471676339 200.000% 1 in 7.4
0.95021293163214 300.000% 1 in 20.1
0.98168436111127 400.000% 1 in 54.6
0.99326205300091 500.000% 1 in 148.4
0.99752124782333 600.000% 1 in 403.4
0.99872735771441 666.666% 1 in 785.8
0.99908811803445 700.000% 1 in 1096.6
0.99966453737210 800.000% 1 in 2981.0
0.99987659019591 900.000% 1 in 8103.1
So if you have it set to expect 1 share every minute, then you'd actually expect on average to have one in every 7.4 shares taking 2min (200%) or longer, and one in every 148.4 shares taking 5min (500%) or longer.
Thats great info, so i guess leaving the diff at 150-200% of your hashrate for one stick would be okay. If you had two stick at 10gh each you then could do 30-40 Diff. Or just leave it at Diff = Hashrate.
I pointed a second stick to my club address, this one also only at 125 freq. I need to get a second hub so I can up-clock these a bit.
I might suggest getting some Y adapters for them aswell if you really want to play with them. They allow you to get much higher freq's.
I still have not had time to set up mine yet for a nice OC.
Y adapter link
http://www.ebay.com/itm/221661361513?
One thing worth mentioning is they work very good. Quality is amazing for the price there.
But it is slow shipping. If you need it this week chances you need to go to another source. I think mine were around 2 weeks to get.
I think i'll grab one then, "winter is coming" and i would not mind running it at x2 speed since cooling is going to become trivial.
I pointed a second stick to my club address, this one also only at 125 freq. I need to get a second hub so I can up-clock these a bit.
I might suggest getting some Y adapters for them aswell if you really want to play with them. They allow you to get much higher freq's.
I still have not had time to set up mine yet for a nice OC.
Y adapter link
http://www.ebay.com/itm/221661361513?
One thing worth mentioning is they work very good. Quality is amazing for the price there.
But it is slow shipping. If you need it this week chances you need to go to another source. I think mine were around 2 weeks to get.
I pointed a second stick to my club address, this one also only at 125 freq. I need to get a second hub so I can up-clock these a bit.
I might suggest getting some Y adapters for them aswell if you really want to play with them. They allow you to get much higher freq's.
I still have not had time to set up mine yet for a nice OC.
Y adapter link
http://www.ebay.com/itm/221661361513?
I pointed a second stick to my club address, this one also only at 125 freq. I need to get a second hub so I can up-clock these a bit.
I might suggest getting some Y adapters for them aswell if you really want to play with them. They allow you to get much higher freq's.
I still have not had time to set up mine yet for a nice OC.
I pointed a second stick to my club address, this one also only at 125 freq. I need to get a second hub so I can up-clock these a bit.
Thanks Kano. That's helpful.
But just a clarification. Since I'm running two sticks and there's just one instance of cgminer, won't the average time to detect a disconnect effectively be cut in half?
If it really makes sense to get to a share every 5 seconds, I want to understand the effect of multiple units on the equation. Unless it makes more sense to plan for the worst case and optimize for a single unit.
Of course with a whopping total of 32 GH/s, clearly I'm not really in this to win. While optimizing is generally good advice, from a pragmatic standpoint it's unlikely that it will mean the difference between finding and not finding a block for me.
But just a clarification. Since I'm running two sticks and there's just one instance of cgminer, won't the average time to detect a disconnect effectively be cut in half?
If it really makes sense to get to a share every 5 seconds, I want to understand the effect of multiple units on the equation. Unless it makes more sense to plan for the worst case and optimize for a single unit.
Of course with a whopping total of 32 GH/s, clearly I'm not really in this to win. While optimizing is generally good advice, from a pragmatic standpoint it's unlikely that it will mean the difference between finding and not finding a block for me.
The pool "talks" to you every 30s (at least) to give you new work.
Keeping your average share rate more active than that is advisable since you have a better chance of finding out about a disconnect sooner.
Personally I'd not put the average share rate less often than every 5s.
Remember that the same statistics apply to shares as to blocks.
A 800%+ Diff block on a pool is rare, but expected to happen 1 in every 2981 blocks.
Same for shares, you'd expect one to show up 8+ times slower than the expected value, 1 in every 2981 shares.
That's not a lot of shares ...
A simple CDF table to refer to:
So if you have it set to expect 1 share every minute, then you'd actually expect on average to have one in every 7.4 shares taking 2min (200%) or longer, and one in every 148.4 shares taking 5min (500%) or longer.
Keeping your average share rate more active than that is advisable since you have a better chance of finding out about a disconnect sooner.
Personally I'd not put the average share rate less often than every 5s.
Remember that the same statistics apply to shares as to blocks.
A 800%+ Diff block on a pool is rare, but expected to happen 1 in every 2981 blocks.
Same for shares, you'd expect one to show up 8+ times slower than the expected value, 1 in every 2981 shares.
That's not a lot of shares ...
A simple CDF table to refer to:
Code:
0.86466471676339 200.000% 1 in 7.4
0.95021293163214 300.000% 1 in 20.1
0.98168436111127 400.000% 1 in 54.6
0.99326205300091 500.000% 1 in 148.4
0.99752124782333 600.000% 1 in 403.4
0.99872735771441 666.666% 1 in 785.8
0.99908811803445 700.000% 1 in 1096.6
0.99966453737210 800.000% 1 in 2981.0
0.99987659019591 900.000% 1 in 8103.1
So if you have it set to expect 1 share every minute, then you'd actually expect on average to have one in every 7.4 shares taking 2min (200%) or longer, and one in every 148.4 shares taking 5min (500%) or longer.
Yeah unless the pool disconnect you after you go silent for so long, but probably not. On solo mining it's pretty much only for monitoring that the hardware is working as intended. You might as well set diff to 10billion, put less load on the pool and use somewhat less bandwidth.
I've settled for 128 for my sticks. At 16 GH/s that seems to result in a share or two within a couple minutes.
I use Minera which will color code the hardware in the web GUI based on how recent they've gotten an accept. With these settings, they usually stay in the green or yellow. So I can tell at a glance that things look OK.
This seems like a good balance. It results in reasonable feedback while not being overly chatty with the pool.
no but think 7- 16 per stick
you don't want ck to auto start the diff at 1k diff it takes 20-50 minutes to adjust.
so 7 to 16 per stick will show shares faster
But at the end of the day "showing shares" is purely cosmetic; your stick is hashing the same regardless if your diff is set to 2 or 2000 (as long as the pool reports back it's hashing, that is). Solo mine your own node and the old share you will ever see would be one greater than network difficulty. Diff won't affect your chance at solving a block, but it does look more reassuring to see the low diff shares float by.
Yeah unless the pool disconnect you after you go silent for so long, but probably not. On solo mining it's pretty much only for monitoring that the hardware is working as intended. You might as well set diff to 10billion, put less load on the pool and use somewhat less bandwidth.
no but think 7- 16 per stick
you don't want ck to auto start the diff at 1k diff it takes 20-50 minutes to adjust.
so 7 to 16 per stick will show shares faster
But at the end of the day "showing shares" is purely cosmetic; your stick is hashing the same regardless if your diff is set to 2 or 2000 (as long as the pool reports back it's hashing, that is). Solo mine your own node and the old share you will ever see would be one greater than network difficulty. Diff won't affect your chance at solving a block, but it does look more reassuring to see the low diff shares float by.
Is there a magic number per stick that we should be setting difficulty to?
I am running my sticks at 250Mhz (about 15GH) and a difficulty of 32
i am going to go ahead and put all of my miners on this for the next few days.. i have a feeling this pool is going to get a block and 1btc is way more then i would mine in that time.
Speaking of rentals, was looking at mining rig rentals (just checking the place out) and came across a 4 compac stick rental 
https://www.miningrigrentals.com/rigs/22284/
https://www.miningrigrentals.com/rigs/22284/
Jump to: