scotty2u2
Newbie
 Offline
Activity: 36
Merit: 0
|
 |
March 13, 2015, 04:52:38 AM |
|
Payout 347282 sent
38f91ec09a55d34e334a7b1858852f707c3f2df0bf8749f786783e8ebb95d489
and confirmed
Thank you!  |
|
|
|
|
|
|
|
Each block is stacked on top of the previous one. Adding another block to the top makes all lower blocks more difficult to remove: there is more "weight" above each block. A transaction in a block 6 blocks deep (6 confirmations) will be very difficult to remove.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
pekatete
|
|
March 13, 2015, 10:32:17 AM |
|
Is the pool down?
EDIT: Looks OK now .... had 0's all over
|
|
|
|
kano (OP)
Legendary
 Online
Activity: 4494
Merit: 1800
Linux since 1997 RedHat 4
|
|
March 13, 2015, 11:30:42 AM |
|
Is the pool down?
EDIT: Looks OK now .... had 0's all over
No, just a ckdb restart which only affects the web page. That ckdb restart means the next ckpool restart can include the change to fix the random problem with user specified difficulty when ckpool restarts. Edit: the pool uptime at the top of the stats page is correct unless it's not showing due to a ckdb restart. I'm not sure what the confusion is, but there was no pool outage. As it says, uptime is 14hrs. As I said, it was a ckdb restart. The pool is made up of 2 parts: 1) ckpool that you mine to that handles all of that on the mining side 2) ckdb that gets all the data and deals with it on the data storage and web side. An outage of 1) affects the miner. An outage of 2) doesn't. Great idea that hey  |
|
|
|
Kexkey
Full Member
Offline
Activity: 237
Merit: 100
Smile while thinking.
|
|
March 13, 2015, 12:21:41 PM |
|
Is the pool down?
EDIT: Looks OK now .... had 0's all over
No, just a ckdb restart which only affects the web page. That ckdb restart means the next ckpool restart can include the change to fix the random problem with user specified difficulty when ckpool restarts. Edit: the pool uptime at the top of the stats page is correct unless it's not showing due to a ckdb restart. I'm not sure what the confusion is, but there was no pool outage. As it says, uptime is 14hrs. As I said, it was a ckdb restart. The pool is made up of 2 parts: 1) ckpool that you mine to that handles all of that on the mining side 2) ckdb that gets all the data and deals with it on the data storage and web side. An outage of 1) affects the miner. An outage of 2) doesn't. Great idea that hey Hi Kano, when ckdb is down, does ckpool keep data in memory until ckdb comes back up and then send all kept data for ckdb to persist? Or does it keep it in a file and you have to manually transfer data to ckdb? Not that it's important, I was just wondering. |
This digital signature is not a digital signature.
|
|
|
kano (OP)
Legendary
Online
Activity: 4494
Merit: 1800
Linux since 1997 RedHat 4
|
|
March 13, 2015, 01:32:09 PM |
|
... I'm not sure what the confusion is, but there was no pool outage. As it says, uptime is 14hrs. As I said, it was a ckdb restart. The pool is made up of 2 parts: 1) ckpool that you mine to that handles all of that on the mining side 2) ckdb that gets all the data and deals with it on the data storage and web side. An outage of 1) affects the miner. An outage of 2) doesn't. Great idea that hey Hi Kano, when ckdb is down, does ckpool keep data in memory until ckdb comes back up and then send all kept data for ckdb to persist? Or does it keep it in a file and you have to manually transfer data to ckdb? Not that it's important, I was just wondering. Firstly, ckdb is a memory resident DB. The postgresql backend is simply the permanent storage that is only read on a restart and written to with all the permanent data. ckpool logs all it's data to hourly logfiles (about 1-1.5GB each at the moment) as well as sending it to ckdb. A ckdb restart reloads the permanent storage DB, then using the info there, it goes and reloads the log files from where the DB was up to. It can currently reload the log files about 50 times faster than they fill up, so a 1hr log file often takes less than a minute. It obviously only needs to look in the last 1 or 2 log files since the down time is always very short It is sometimes 2 logfiles since it may happen just around the time of the log file change over. At the same time, it has been getting all the new incoming data from ckpool queued up. When it hits a match in the log file vs the 1st incoming queued message from ckpool, it knows it has all the data it needs from the log files. At this point everything is back to working - but out of sync. It then has to sync/catch up on all the data queued in ram, that was transferred from ckpool while ckdb was reloading the log files. That sync number is the number it shows on the bottom left of the web site That number also grows whenever ckdb gets behind processing the data from ckpool, usually due to DB write delays. Currently the reload takes from 3 to 5 minutes and the sync usually only takes a minute or two after that to get back down to zero. |
|
|
|
obfuscated
Newbie
Offline
Activity: 38
Merit: 0
|
|
March 13, 2015, 02:44:55 PM |
|
tlhIlwI, If I understand correctly, you mine with kano but set the p= value on your westhash entry to 0.0115? So I'm assuming you find you get better payouts with kano atm.
It's a bit more complicated but the short answer is yes... sort of. The long answer is .... Thanks for explaining this. |
|
|
|
|
|
pekatete
|
|
March 13, 2015, 04:16:21 PM |
|
Get in there! Feels good to get one at 1.08% diff!
|
|
|
|
jonnybravo0311
Legendary
Offline
Activity: 1344
Merit: 1023
Mine at Jonny's Pool
|
|
March 13, 2015, 04:26:10 PM |
|
Get in there! Feels good to get one at 1.08% diff!
Wow... only half a million shares and block. Nice |
Jonny's Pool - Mine with us and help us grow! Support a pool that supports Bitcoin, not a hardware manufacturer's pockets! No SPV cheats. No empty blocks.
|
|
|
|
tlhIlwI
|
|
March 13, 2015, 04:28:08 PM |
|
Get in there! Feels good to get one at 1.08% diff!
Nice! Makes the stats table look a lot better It's not showing up on rewards page though. |
|
|
|
|
bitwitt
|
|
March 13, 2015, 04:30:32 PM |
|
It appears that Blockchain and Blocktrail both are not reporting an orphan at that height yet.
FYI After our last orphan this pool went on a BLOCK rampage. If I remember we had +1% of network of blocks found with much less hash rate. Time to start the block PARTY !  |
|
|
|
|
|
pekatete
|
|
March 13, 2015, 04:31:10 PM |
|
Get in there! Feels good to get one at 1.08% diff!
Nice! Makes the stats table look a lot better It's not showing up on rewards page though. That table is gonna look better still ..... and last will show in rewards after current block is solved. |
|
|
|
jonnybravo0311
Legendary
Offline
Activity: 1344
Merit: 1023
Mine at Jonny's Pool
|
|
March 13, 2015, 04:32:13 PM |
|
Get in there! Feels good to get one at 1.08% diff!
Nice! Makes the stats table look a lot better It's not showing up on rewards page though. Probably just hasn't been updated yet... the block is staying here, though... And, as I'm writing this post, the rewards page is properly updated. |
Jonny's Pool - Mine with us and help us grow! Support a pool that supports Bitcoin, not a hardware manufacturer's pockets! No SPV cheats. No empty blocks.
|
|
|
|
tlhIlwI
|
|
March 13, 2015, 04:39:36 PM |
|
What is the shortest diff block this pool has ever had?
Also, what do the green dots at the left of the header mean? Every once in a while the middle one is yellow or a red Vader.
|
|
|
|
|
PatMan
|
|
March 13, 2015, 04:52:17 PM |
|
Boom boom!! Quick fire blocks incoming....... |
|
|
|
Prelude
Legendary
Offline
Activity: 1596
Merit: 1000
|
|
March 13, 2015, 06:04:01 PM |
|
You guys can thank me for the 1.06% block. I just bought 4 SP20Es for 1.06 BTC each, it has to be related. LOL   |
|
|
|
|
jonnybravo0311
Legendary
Offline
Activity: 1344
Merit: 1023
Mine at Jonny's Pool
|
|
March 13, 2015, 06:20:57 PM |
|
You guys can thank me for the 1.06% block. I just bought 4 SP20Es for 1.06 BTC each, it has to be related. LOL And in other completely related news, the expected earnings of 1TH/s per day is... 0.0106 BTC... coincidence? I think NOT! |
Jonny's Pool - Mine with us and help us grow! Support a pool that supports Bitcoin, not a hardware manufacturer's pockets! No SPV cheats. No empty blocks.
|
|
|
thedreamer
Legendary
Offline
Activity: 1694
Merit: 1002
Go Big or Go Home.....
|
|
March 13, 2015, 06:33:27 PM |
|
You guys can thank me for the 1.06% block. I just bought 4 SP20Es for 1.06 BTC each, it has to be related. LOL And in other completely related news, the expected earnings of 1TH/s per day is... 0.0106 BTC... coincidence? I think NOT! Wow, what a steal on both ends, nice. Do they have any more? Lol |
Go Big or Go Home.
|
|
|
kano (OP)
Legendary
Online
Activity: 4494
Merit: 1800
Linux since 1997 RedHat 4
|
|
March 13, 2015, 09:31:38 PM |
|
Get in there! Feels good to get one at 1.08% diff!
Nice! Makes the stats table look a lot better It's not showing up on rewards page though. It takes either ~10 minutes or just after the next network block (whichever is longer) before ckdb generates the Rewards data. |
|
|
|
Prelude
Legendary
Offline
Activity: 1596
Merit: 1000
|
|
March 13, 2015, 09:40:34 PM |
|
You guys can thank me for the 1.06% block. I just bought 4 SP20Es for 1.06 BTC each, it has to be related. LOL *snip* And in other completely related news, the expected earnings of 1TH/s per day is... 0.0106 BTC... coincidence? I think NOT! Ha! Look at that! You guys can thank me for the 1.06% block. I just bought 4 SP20Es for 1.06 BTC each, it has to be related. LOL *snip* And in other completely related news, the expected earnings of 1TH/s per day is... 0.0106 BTC... coincidence? I think NOT! Wow, what a steal on both ends, nice. Do they have any more? Lol Unfortunately not, if they did they'd be on their way to me. |
|
|
|
|
kano (OP)
Legendary
Online
Activity: 4494
Merit: 1800
Linux since 1997 RedHat 4
|
|
March 13, 2015, 09:46:58 PM |
|
What is the shortest diff block this pool has ever had?
Also, what do the green dots at the left of the header mean? Every once in a while the middle one is yellow or a red Vader.
They are 3 VERY raw statistics about data from ckpool to ckdb. The top one is the 'last heartbeat', the middle one is the 'last share' and the bottom one is the 'last workinfo' Firstly, if they are orange or red, they will usually switch back to green pretty quickly. Look at the sync value at the bottom of the page and that will usually be high and the reason for any going orange or red. The heartbeat will rarely change colour. Heartbeats are sent ~once every second from ckpool to ckdb. It goes orange after 5 seconds and red after 10 seconds. We get (current value right now) ~700 shares per second, so last share should only ever get above 1 second if there's a queue (sync) building up due to DB I/O delays. If it gets above 8 seconds it goes orange, and above 10 seconds it goes red. Workinfo is the new work built every ~30 seconds. So it goes orange after 36 seconds and red after 46 seconds. If they are orange/red and the sync at the bottom is 0/green then you know my phone and ipad are beeping and my screen is showing popups. The alert times on that are a little higher - since as you have seen orange/red happens every so often on the middle one (last share) - usually when DB I/O is delaying ckdb a bit. But that's OK since it always catches back up - and of course has no effect on ckpool at all. If ckpool locks up or dies and restarts then they will go orange then red and the sync at the bottom will be 0/green until ckpool has restarted. |
|
|
|
|
