KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fee - Worldwide - 2435 blocks

[DevonMiner]

One SP30 failed over, but that's only one out of my miners.

EDIT: SP30s failed over, SP20s didn't.

[1714044466]

1714044466

[1714044466]

1714044466

[mdude77]

Just restarted ckpool to update/add more fixes in the running version.
As usual, most shouldn't failover, and this one has more changes to try and reduce the few that do failover.

Mine failed over, and both lost their custom work size.

M

[kano]

Just restarted ckpool to update/add more fixes in the running version.
As usual, most shouldn't failover, and this one has more changes to try and reduce the few that do failover.

Mine failed over, and both lost their custom work size.

M

Hmm, there was another fix in ckpool for that in the new version - guess it didn't work either.

The failover issue seems that it will change soon to always being a failover on restart.
I already try to avoid restarting ckpool as much as possible, but I guess I'll take that into consideration each time now also.

Payout 341766 sent and confirmed

[philipma1957]

Just restarted ckpool to update/add more fixes in the running version.
As usual, most shouldn't failover, and this one has more changes to try and reduce the few that do failover.

Mine failed over, and both lost their custom work size.

M

Hmm, there was another fix in ckpool for that in the new version - guess it didn't work either.

The failover issue seems that it will change soon to always being a failover on restart.
I already try to avoid restarting ckpool as much as possible, but I guess I'll take that into consideration each time now also.

Payout 341766 sent and confirmed

got it thank you.

[sloopy]

When I added my first SP20 here it takes a while to build up to the hashrate I usually see on other pools much faster.
I'm not complaining I want to understand.
Is it because I do not set a difficulty? Starting at 1k should be perfect for an SP20 and be right there at 1.3 1.6 however you have it setup.
I restored an S3, new used fans, re-pasted the chips, put it on the pool and local hashrate was straight to 450ish right away.
I try to pay attention and I know I've read the pool shows what matters. Does it truly take that long at any pool, do I have a poor connection, or something set wrong?

Thanks

[stan258]

When I added my first SP20 here it takes a while to build up to the hashrate I usually see on other pools much faster.
I'm not complaining I want to understand.
Is it because I do not set a difficulty? Starting at 1k should be perfect for an SP20 and be right there at 1.3 1.6 however you have it setup.
I restored an S3, new used fans, re-pasted the chips, put it on the pool and local hashrate was straight to 450ish right away.
I try to pay attention and I know I've read the pool shows what matters. Does it truly take that long at any pool, do I have a poor connection, or something set wrong?

Thanks

pools gauge hash rate based on how fast our hardware submits work.  Here you get one hr and 5 min in the upper right after you log in.  When I take a miner down to update or fiddle with something it usually takes about an hour or so to get back up to what the miner is reporting.  This also varies as the miner may just get a glut of high diff shares or visa verse. 

[kano]

When I added my first SP20 here it takes a while to build up to the hashrate I usually see on other pools much faster.
I'm not complaining I want to understand.
Is it because I do not set a difficulty? Starting at 1k should be perfect for an SP20 and be right there at 1.3 1.6 however you have it setup.
I restored an S3, new used fans, re-pasted the chips, put it on the pool and local hashrate was straight to 450ish right away.
I try to pay attention and I know I've read the pool shows what matters. Does it truly take that long at any pool, do I have a poor connection, or something set wrong?

Thanks

The diff itself makes no difference except on a few of the miners that have faulty firmware and need it to be above some value.

Some of the bitmain miner firmware versions have a minor issue that if the diff is a power of 2, then best share stays on zero.

If you have higher diff, then you'll expect to submit fewer shares, if you have lower diff then you'll expect to submit more shares.
The statistical expectation is that High x Few ~= Low x Many ... and you can't pick a different diff to expect to get better results.

One thing to look at on the pool is the Invalid % of the worker.
If the miner gets a lot of invalids when it starts, it may take a while to get up to speed.

Another thing to look at is the API of cgminer - though some of the manufacturer hacked versions of cgminer don't report that correctly.
Anyway, the API may also show you what is going on with the miner.

Lastly, there is also a simple calculation you can do with any cgminer if you can access the API summary.
DifficultyAccepted * 2^32 / Elapsed
This is the paid hash rate at the pool - the shares the pool accepted over the time since cgminer started.

Edit: cgminer miner.php the "Kano" button shows that value

[-ck]

Block
https://blockchain.info/block-index/605734/00000000000000000e228a6abad006cdb35603dd1069f4081bfc76ea8935eae5
edit: confirmed

[kano]

Block
https://blockchain.info/block-index/605734/00000000000000000e228a6abad006cdb35603dd1069f4081bfc76ea8935eae5
edit: confirmed

Yay a green one!

[kipper01]

Block
https://blockchain.info/block-index/605734/00000000000000000e228a6abad006cdb35603dd1069f4081bfc76ea8935eae5
edit: confirmed

Yay a green one!

Ok I am a noob...Just got my first miner up and running. (S5) Where can I read up on green/red/bright green and what all that means to me?

[kano]

Block
https://blockchain.info/block-index/605734/00000000000000000e228a6abad006cdb35603dd1069f4081bfc76ea8935eae5
edit: confirmed

Yay a green one!

Ok I am a noob...Just got my first miner up and running. (S5) Where can I read up on green/red/bright green and what all that means to me?

Well ... it says on the top of the blocks page what they are

But the % is simply the % of expected shares per block.
At the moment the average expected shares per block is 41272873894.7
So if we are exactly 100% that means that many shares were accepted by the pool from the previous block to that block.
If it's only 50% then we found the block twice as fast as the expected average.
If it's 200% then it took twice as long as the expected average.
< 100% is good luck
> 100% is bad luck

Some pools display that value inverted so that < 100% is bad and > 100% is good - but then you can't easily see how good or bad the pool is doing over a range of blocks.
Worse with the inverted % is that it can hide how badly the pool has been doing for months ... without people noticing ... ...

With our percentage you can roughly see how well the pool is doing by looking at the blocks page ... and just adding up numbers to see roughly how well a range of blocks went.
So if 5 blocks took 500% then they averaged out ok.
If 5 blocks took 100% then it went REALLY well

The last 5 blocks add up to ~739% so not very good luck almost 150% each
(note that adding up the % isn't highly accurate but a reasonable rough estimate)

The previous 5 blocks added up to under 300% - quite good luck

Thus the last 10 were ... ~1040% so quite OK

[philipma1957]

Block
https://blockchain.info/block-index/605734/00000000000000000e228a6abad006cdb35603dd1069f4081bfc76ea8935eae5
edit: confirmed

Yay a green one!

Ok I am a noob...Just got my first miner up and running. (S5) Where can I read up on green/red/bright green and what all that means to me?

look at  the block  column on the right in the screenshot.  @ Kano  I am color blind and some of those color shades don't work for me. so  thank you for putting in the actual %





full image
http://imageshack.com/a/img673/2750/cBd5gP.png

[kano]

...
  @ Kano  I am color blind and some of those color shades don't work for me. so  thank you for putting in the actual %
...

Well the text colour is supposed to be clear to see on the background.
The white on red seems to work well for all ranges on red.
The white on green is hard to read when green gets above 190/255 so it switch to blue text when it's brighter.
Are you able to differentiate them with the way I've chosen that?

[philipma1957]

...
  @ Kano  I am color blind and some of those color shades don't work for me. so  thank you for putting in the actual %
...

Well the text colour is supposed to be clear to see on the background.
The white on red seems to work well for all ranges on red.
The white on green is hard to read when green gets above 190/255 so it switch to blue text when it's brighter.
Are you able to differentiate them with the way I've chosen that?

yeah you did a perfect way for my eyes.

 So when I look at the blocks any that I don't see correctly color wise I do read the text. 

A real P.I.T.A. as certain shades of green vs red or blue vs purple  are basically oh well to me. 

Your system is very good for me thanks again.

[kipper01]

Block
https://blockchain.info/block-index/605734/00000000000000000e228a6abad006cdb35603dd1069f4081bfc76ea8935eae5
edit: confirmed

Yay a green one!

Ok I am a noob...Just got my first miner up and running. (S5) Where can I read up on green/red/bright green and what all that means to me?

Well ... it says on the top of the blocks page what they are

But the % is simply the % of expected shares per block.
At the moment the average expected shares per block is 41272873894.7
So if we are exactly 100% that means that many shares were accepted by the pool from the previous block to that block.
If it's only 50% then we found the block twice as fast as the expected average.
If it's 200% then it took twice as long as the expected average.
< 100% is good luck
> 100% is bad luck

Some pools display that value inverted so that < 100% is bad and > 100% is good - but then you can't easily see how good or bad the pool is doing over a range of blocks.
Worse with the inverted % is that it can hide how badly the pool has been doing for months ... without people noticing ... ...

With our percentage you can roughly see how well the pool is doing by looking at the blocks page ... and just adding up numbers to see roughly how well a range of blocks went.
So if 5 blocks took 500% then they averaged out ok.
If 5 blocks took 100% then it went REALLY well

The last 5 blocks add up to ~739% so not very good luck almost 150% each
(note that adding up the % isn't highly accurate but a reasonable rough estimate)

The previous 5 blocks added up to under 300% - quite good luck

Thus the last 10 were ... ~1040% so quite OK

Thanks kano.  I just needed someone to elaborate a little on what it all meant.  Makes sense now

[kano]

Payout 341855 sent and confirmed

[philipma1957]

Payout 341855 sent and confirmed

received thank you

[DevonMiner]

lightsword maybe rented their/his/her equipment once more ... total pool hash rate down again for a while.

Would be nice if a few more big hitters pointed hardware this way.

[philipma1957]

lightsword maybe rented their/his/her equipment once more ... total pool hash rate down again for a while.

Would be nice if a few more big hitters pointed hardware this way.

   well we still have 2.7 ph   that is about 1 block a day .

[-ck]

When I added my first SP20 here it takes a while to build up to the hashrate I usually see on other pools much faster.
I'm not complaining I want to understand.
Is it because I do not set a difficulty? Starting at 1k should be perfect for an SP20 and be right there at 1.3 1.6 however you have it setup.
I restored an S3, new used fans, re-pasted the chips, put it on the pool and local hashrate was straight to 450ish right away.
I try to pay attention and I know I've read the pool shows what matters. Does it truly take that long at any pool, do I have a poor connection, or something set wrong?

The 1 minute you see there means "rolling exponential average with 1 minute time constant" which means it gives you a more accurate estimate than grabbing just the last minute's shares and estimating a hashrate from them, but that also means if you start at zero it takes ~5 time constants to plateau meaning 5 minutes. The hashrate used as the accurate current hashrate on the website is the 5 minute time constant one so it takes even longer to rise. It does not mean your hashrate is less than on other pools during that time, it's just far more likely to give you an accurate estimate of hashrate. The per hashrate stats are now updated every minute on the website after one of the many changes recently added to both ckpool and ckdb instead of the old way which updated them every 10 minutes.

Specifically with the sp20, they go through a process of fine tuning each time they start as well so it takes them longer than S3s to get to their final hashrate.