DobZombie
|
|
October 30, 2012, 08:56:56 AM |
|
I could have sworn it was vain. Vein is the thing blood flows through, vane is a portion of a propeller/impeller assembly or a banner to tell wind direction, vain is either idle and useless or conceited.
That's the one!
|
Tip Me if believe BTC1 will hit $1 Million by 2030 1DobZomBiE2gngvy6zDFKY5b76yvDbqRra
|
|
|
-ck
Legendary
Offline
Activity: 4256
Merit: 1645
Ruu \o/
|
|
October 30, 2012, 09:10:26 AM |
|
My rig still hovers at diff 1 on emc1 despite submitting ~37 shares per minute. I thought it was trying to keep shares below 20/m?
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
The00Dustin
|
|
October 30, 2012, 10:15:04 AM |
|
My rig still hovers at diff 1 on emc1 despite submitting ~37 shares per minute. I thought it was trying to keep shares below 20/m?
Yeah, US1 is set at I think 30 SPM target over a 3 minute period, so that's about right.
On another note, I am going to try moving the DB in a few minutes, so the website will go offline. Mining nodes should remain up though. I'm not saying there isn't a problem, but this was his response a while back, and I don't know if he made it before you edited your post to say "nvm it took a while but went up to 2." I think it was originally set to 20, and I looked for the post where he mentioned the changed numbers, but couldn't find it.
|
|
|
|
-ck
Legendary
Offline
Activity: 4256
Merit: 1645
Ruu \o/
|
|
October 30, 2012, 10:16:05 AM |
|
My bad. Got lost in the noise.
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
DobZombie
|
|
October 30, 2012, 03:39:29 PM |
|
Website is down?
Machines are still hashing on EMC
|
Tip Me if believe BTC1 will hit $1 Million by 2030 1DobZomBiE2gngvy6zDFKY5b76yvDbqRra
|
|
|
DobZombie
|
|
October 30, 2012, 03:40:53 PM |
|
Spoke to soon, she's back up
|
Tip Me if believe BTC1 will hit $1 Million by 2030 1DobZomBiE2gngvy6zDFKY5b76yvDbqRra
|
|
|
cabin
|
|
October 30, 2012, 06:36:11 PM |
|
Inaba, did PayPal ever give you back your money when they froze everything? Just curious.
|
|
|
|
Inaba (OP)
Legendary
Offline
Activity: 1260
Merit: 1000
|
|
October 30, 2012, 10:56:14 PM |
|
Nope, they are still holding on to my funds. @#%#@$ Paypal.
Con - are you seeing what you should be seeing or are you still experiencing a problem?
|
If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.
|
|
|
-ck
Legendary
Offline
Activity: 4256
Merit: 1645
Ruu \o/
|
|
October 31, 2012, 12:56:50 AM |
|
Nope, they are still holding on to my funds. @#%#@$ Paypal.
Con - are you seeing what you should be seeing or are you still experiencing a problem?
Depends on what you define as a problem. It hovers mostly around diff 1 and occasionally rises to diff 2 at 37 shares per minute. But you said your target share rate is 30pm for US1 which I thought you said originally was slated for 20pm.
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
Inaba (OP)
Legendary
Offline
Activity: 1260
Merit: 1000
|
|
October 31, 2012, 03:36:15 AM |
|
US1 is currently set to 20 spm over a 180 second test window. You are connected to US1 and not seeing an adjustment even at almost twice that?
Although... now that I think about it, that makes sense, if you aren't doubling the target then you won't get to 2 very often, since it would bring you in under 20 SPM otherwise, so I think that makes sense.
|
If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.
|
|
|
-ck
Legendary
Offline
Activity: 4256
Merit: 1645
Ruu \o/
|
|
October 31, 2012, 03:51:00 AM |
|
US1 is currently set to 20 spm over a 180 second test window. You are connected to US1 and not seeing an adjustment even at almost twice that?
Although... now that I think about it, that makes sense, if you aren't doubling the target then you won't get to 2 very often, since it would bring you in under 20 SPM otherwise, so I think that makes sense.
Ok, wondering whether you used any hysteresis for diff up versus diff down and whether the diff target is a "keep below 20 shares". There's nothing actually wrong here then, just my misinterpretation.
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
Inaba (OP)
Legendary
Offline
Activity: 1260
Merit: 1000
|
|
October 31, 2012, 05:08:36 AM |
|
Well, the sliding window is currently set at 180 seconds, so, if I understand what you're asking, then yes to a limited degree.
|
If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.
|
|
|
cabin
|
|
October 31, 2012, 05:22:51 PM |
|
Sorry to hear that.. hope they give it back one day. Doesn't seem right at all. Nope, they are still holding on to my funds. @#%#@$ Paypal.
Con - are you seeing what you should be seeing or are you still experiencing a problem?
|
|
|
|
-ck
Legendary
Offline
Activity: 4256
Merit: 1645
Ruu \o/
|
|
October 31, 2012, 11:22:17 PM |
|
Well, the sliding window is currently set at 180 seconds, so, if I understand what you're asking, then yes to a limited degree.
No, by hysteresis I mean a different threshold for lowering diff versus raising diff. i.e. if the shares are > 20 per minute to increase diff, but then to only lower diff if they drop to < 10. There will be less bouncing around of diff values that way.
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
Inaba (OP)
Legendary
Offline
Activity: 1260
Merit: 1000
|
|
October 31, 2012, 11:36:32 PM |
|
Ah, got it... no, it just uses a sliding window. Is there some drawback to bouncing around? The work is accepted for old difficulty work, so it doesn't matter if there is a difficulty change, since the difficulty is tied to the work sent out. You might be currently working on Difficulty 3 and sending back difficulty 2 shares from an older set of work that hasn't been sent back yet.
|
If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.
|
|
|
-ck
Legendary
Offline
Activity: 4256
Merit: 1645
Ruu \o/
|
|
October 31, 2012, 11:44:56 PM |
|
Ah, got it... no, it just uses a sliding window. Is there some drawback to bouncing around? The work is accepted for old difficulty work, so it doesn't matter if there is a difficulty change, since the difficulty is tied to the work sent out. You might be currently working on Difficulty 3 and sending back difficulty 2 shares from an older set of work that hasn't been sent back yet.
Not with getwork, but with GBT (and stratum) the work is tied with the block template they get, so if they ask for an updated block template, and are currently working on different difficulty shares, they lose work across diff changes (mainly on diff drop) since internally the pool only has the notion of the current difficulty target expected from the miner unless you go out of your way to add leeway expecting old target diff work for some grace period.
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
Inaba (OP)
Legendary
Offline
Activity: 1260
Merit: 1000
|
|
November 01, 2012, 12:41:27 AM |
|
EMC tracks difficulty per job, not per user. So it works on both the getwork and GBT side, so it doesn't matter which protocol you use or when you submit the work, as long as it's not stale, it will accept it if it's under the difficulty for a particular job. If you're discarding work when you receive new work without submitting it then yes you'd lose shares, but if you submit it even after you get new work, it's likely still valid within the stale window.
|
If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.
|
|
|
poon-TANG
|
|
November 01, 2012, 01:08:03 AM |
|
US 1 working here
|
|
|
|
kano
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
|
November 01, 2012, 10:54:46 AM |
|
EMC tracks difficulty per job, not per user. So it works on both the getwork and GBT side, so it doesn't matter which protocol you use or when you submit the work, as long as it's not stale, it will accept it if it's under the difficulty for a particular job. If you're discarding work when you receive new work without submitting it then yes you'd lose shares, but if you submit it even after you get new work, it's likely still valid within the stale window.
Woo - nice. That's my argument against Stratum at the moment, the fact that difficulty is separated from work. Now if we could just get GBT to reduce the amount of data that it needs to send to the miner (more than GetWork with roll-n-time), use a better protocol ..., and solve the mystery of ignored transactions; then if Stratum's diff was also fixed we'd have 2 closely competitive options ...
|
|
|
|
freshzive
|
|
November 01, 2012, 09:55:41 PM |
|
could this 14 hour round end please? thanks
|
|
|
|
|