That last block we just got, 339388, https://blockchain.info/block/00000000000000000088ea4d769abcf758d8d18d68d457abf083e515c4d12437
it the 100th successful block we've found (plus one orphan after the 1st block we found)
Happy 100 everyone
Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 2191. (Read 5352747 times)
January 17, 2015, 03:55:13 PM
... and a bit of news, especially for those who have been mining here since we started in September.
That last block we just got, 339388, https://blockchain.info/block/00000000000000000088ea4d769abcf758d8d18d68d457abf083e515c4d12437
it the 100th successful block we've found (plus one orphan after the 1st block we found)
Happy 100 everyone
That last block we just got, 339388, https://blockchain.info/block/00000000000000000088ea4d769abcf758d8d18d68d457abf083e515c4d12437
it the 100th successful block we've found (plus one orphan after the 1st block we found)
Happy 100 everyone
January 17, 2015, 02:47:21 PM
As I'm relatively new to mining, sorry if this is a silly question that just everyone knows.
Looking at the worker page on kano.is it says my total is 7th/sec, but looking at each miner individually they show a total of 11.4th/sec, where does that discrepancy come from?
Looking at the worker page on kano.is it says my total is 7th/sec, but looking at each miner individually they show a total of 11.4th/sec, where does that discrepancy come from?
I think one is an instant hash rate and one is an average. I would imagine after a few shifts they'll be closer to matching.
5min average/ 1Hr average Kano said it was dynamic few pages back.
The 1hr value should be the value of interest.
However, if you haven't been mining for an hour yet, it doesn't show the "1hr" value
January 17, 2015, 12:26:22 PM
As I'm relatively new to mining, sorry if this is a silly question that just everyone knows.
Looking at the worker page on kano.is it says my total is 7th/sec, but looking at each miner individually they show a total of 11.4th/sec, where does that discrepancy come from?
Looking at the worker page on kano.is it says my total is 7th/sec, but looking at each miner individually they show a total of 11.4th/sec, where does that discrepancy come from?
I think one is an instant hash rate and one is an average. I would imagine after a few shifts they'll be closer to matching.
5min average/ 1Hr average Kano said it was dynamic few pages back.
January 17, 2015, 11:27:04 AM
As I'm relatively new to mining, sorry if this is a silly question that just everyone knows.
Looking at the worker page on kano.is it says my total is 7th/sec, but looking at each miner individually they show a total of 11.4th/sec, where does that discrepancy come from?
Looking at the worker page on kano.is it says my total is 7th/sec, but looking at each miner individually they show a total of 11.4th/sec, where does that discrepancy come from?
I think one is an instant hash rate and one is an average. I would imagine after a few shifts they'll be closer to matching.
January 17, 2015, 10:32:55 AM
And another! Turning into a good day.
Turning into a good day. This was nice to wake up to ...
looks like you put a lot of work in Kano, hope you were able to take a break
It looks like he spent his whole Saturday working on it.
I too hope he took some breaks throughout the day.
January 17, 2015, 10:03:38 AM
And another! Turning into a good day.
Turning into a good day. This was nice to wake up to ...
looks like you put a lot of work in Kano, hope you were able to take a break
And another one this morning too
January 17, 2015, 07:12:37 AM
And another! Turning into a good day.
Turning into a good day. This was nice to wake up to ...
looks like you put a lot of work in Kano, hope you were able to take a break
January 17, 2015, 05:52:32 AM
Payouts 339142, 339178, 339183 just sent
and confirmedEdit: oh and all 3 used the new 50 minutes shifts so the 5N value was a bit bigger again due to the rounding up to the shift boundary
January 17, 2015, 04:20:31 AM
January 17, 2015, 03:46:38 AM
And another! Turning into a good day.
Turning into a good day. January 17, 2015, 02:21:17 AM
As I'm relatively new to mining, sorry if this is a silly question that just everyone knows.
Looking at the worker page on kano.is it says my total is 7th/sec, but looking at each miner individually they show a total of 11.4th/sec, where does that discrepancy come from?
Well the two pages do work out the result differently, but it also depends on things like switching workers.Looking at the worker page on kano.is it says my total is 7th/sec, but looking at each miner individually they show a total of 11.4th/sec, where does that discrepancy come from?
If you have the same devices doing the same mining on the same workers they should be the same.
It could be caused if you are switching workers (stopping one then switching to another)
Meanwhile - I got interrupted by the best interruption
We found another block this time at just over 100% expected so still looking good for this week so far.
... back to working on getting the shifts going ...
More shift work will be required after that, but this should mean I can do the outstanding payouts
(i.e. get the correct numbers to do the payouts)
Hopefully my next reply (though will be a while) will be the Payouts
January 16, 2015, 11:42:56 PM
As I'm relatively new to mining, sorry if this is a silly question that just everyone knows.
Looking at the worker page on kano.is it says my total is 7th/sec, but looking at each miner individually they show a total of 11.4th/sec, where does that discrepancy come from?
Looking at the worker page on kano.is it says my total is 7th/sec, but looking at each miner individually they show a total of 11.4th/sec, where does that discrepancy come from?
January 16, 2015, 11:26:44 PM
Oh well, I have a couple Boxx 1u Remote workstations w/ 16x1GB each but turns out its ol' 400Mhz.
January 16, 2015, 11:07:51 PM
I don't suppose you would still be using DDR400 ECC?
No 
The server has 48GB ram but I seem to able able to use a lot more than that easily enough with ckdb ... the whole reason for the 50min shift change in the first place
Looks like I'll have to do the shifts change to be able to do the payout, just can't get it to load the excessive amount of data (that the 50min shifts will dramatically reduce) without affecting ckpool.
Still working on it ...
January 16, 2015, 10:37:28 PM
I don't suppose you would still be using DDR400 ECC?
January 16, 2015, 10:23:32 PM
Thanks for the updates.
I unfortunately managed to take down the pool (more than once) due to ckdb using too much ram(which is what the shift change this afternoon is all about)
Everyone should have failed back, each time, quickly though, since ckpool now has a change to make the initial connections to it way faster when it starts up.
I had to, again, limit the ckdb reload, but I can work around that and make the payouts, but will be a little longer yet to do them.
January 16, 2015, 09:44:45 PM
Thanks for the updates.
January 16, 2015, 09:38:18 PM
OK, ckdb restart coming up in the next few minutes (web stats unavailable then out of sync for a while)
Then I'll do the 3 payouts due once ckdb restart has completed and synced.
As usual, no expected outage or any affect on mining.
Then I'll do the 3 payouts due once ckdb restart has completed and synced.
As usual, no expected outage or any affect on mining.
January 16, 2015, 08:44:08 PM
Pool seems to have lost almost 2 Petahash/sec.
Usually it's someone gambling on solo pool with hashes that come from our biggest hasher on this pool, and there's currently >2PH on solo pool which is consistent. It's only ever temporary. January 16, 2015, 08:40:21 PM
Pool seems to have lost almost 2 Petahash/sec.
Jump to: