Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 2191. (Read 5352097 times)

Oh well, I have a couple Boxx 1u Remote workstations w/ 16x1GB each but turns out its ol' 400Mhz.

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 ...

I don't suppose you would still be using DDR400 ECC?

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.

Thanks for the updates.

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.

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.

Pool seems to have lost almost 2 Petahash/sec.

OK first update, I've still not paid out 339142 yet.
But since 339178 and 339183 are coming up shortly, I'll pay all 3 with the old 30 second shifts since the other 2 will probably be ready to pay by the time I'm ready to pay 339142 (probably another hour or so)

Thus in the above comment about the payout switch to 50 minutes shifts, it will be starting with the payout of block 339225 instead of 339178 (339178 is the block "after 339142")

Relax man, Kano does the payments manually....its not automated.
You will get them don't worry.
Its a very successful pool when it comes to block-finding....probably the best out there!
I suggest the address you mine under is labeled "CK-Kano Pool"

Watch your wallet and enjoy ! 

The next payout, 339142, will be delayed a few hours.

Short version: testing code on test pool, awaiting that test result, then will restart ckdb on live pool and then can run payout.

Extra comment: these changes below are all ckdb related, so as usual should not affect your mining, just the usual data outages on the web site and delays syncing the web site while ckdb does it's reloading each time.

Long version:
During the drama yesterday I restarted ckdb in a 'restricted' mode (the -w option) where I can tell it to only load a limited amount of share info.
I set it to only load to block 338977 (currently ~12million records) which means that since the 339142 payout will extend back before the point when we found block 338977, I'll need to restart ckdb in full mode before I can do the payout.
Late last night (1:30am) I manually ran the markers code to reduce all the sharesummaries, older than payout 338977, to a small number of markersummaries, so a full restart of ckdb will have all the data needed (of course) but also not use up all the ram loading more than 50million sharesummaries, that's back down to about 15million (the conversion of sharesummaries to markersummaries is usually around 1000th i.e. 1 million sharesummaries averages out to be about 1000 markersummaries - the shift changes will convert 1,000,000 sharesummaries to about 10,000 markersummaries)
I also (late last night) copied the whole pool database to a test server that has the new updated ckdb shift code (that's now completed) and I am awaiting it to run fully on the test server to see there's no issues with that.
Once that's done, I'll restart ckdb on the live pool (but without the final shift changes) and do the 339142 payout.

Later today, I'll do the shift code update on the live pool - after the test server shows all things worked as expected.
I've been doing a lot of testing there already, but I think this last version should be all OK, and I wanted to test it on the full live db, copied to the test server.

This will be the implementation of the 50 minute shifts I've mentioned for a while, but finally got it ready to go.

Currently, payouts extend a bit beyond the 5N 500% PPLNS point I keep talking about. On average by half a shift.
Shifts currently are usually 30s so on average it's 15s of extra shares included in each payout.

The new shift will be (usually) 50 minutes, so on average the payout will extend half a shift, or 25 minutes extra, back past the 5N 500% PPLNS point.

So the payouts for the blocks after 339142 will use the new 50 minute shifts - and they will also be delayed (later) today until after I do the shift changes.

I'll update later as things progress.

P.S. whenever I say "today", "tonight", etc I am of course talking about my local time which is AEST or currently UTC+11/GMT+11
(and currently 9:30am 17-Jan)

Many thanks kano, i found my wallet there, i have from this and from the 339142 last two still for confirmations rigth?

338977
https://blockchain.info/tx/cd38750a19285691bfc5e015f6a4db0b58a182f391aa57fc1a54027457f2fb2a

hi, sorry if i disturb someone but, i dont have clever the payments, where the pool do the payments? im running my rig in ckpool im check the stats and 11th 10workers all correct but in the last 24h i didnt get any payment, im wait payments from the block  338977

please confirm me if im wrong i cant check stats

You just never know do you.
I think of it like to lottery and a miner is the price of entry.

just goes to show that anyone could of won! 

damn greenegg barely missed out on winning that prize...

It was only 210% - wait until we hit a 800% one day (maybe) then you'll be wondering why you were mining
(longest so far is 525%)

Meanwhile - I think that's a record
New block (awaiting confirm) by a user with 2.18THs!

Edit: confirmed

Nice to see the blocks coming again, that 27 hours felt like forever.

I love it when the pool gets blocks......like
bam-dee bam-BAM