mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
July 14, 2014, 10:12:49 PM |
|
How can I look up my hashrate quickly and easily for a specific worker? I see my payout address listed on all the p2pool nodes (i.e. http://107.170.116.123:9332/static/ under Payouts if a block were found NOW) Is there a json api or some URL i could bookmark that would quickly give me my hashrate? I want to implement some sort of warning system to alert me if my workers die. If someone knows how to do this, that would be most appreciated My M's Pool Monitor can do the monitoring/alerting for you. (see sig) If you're using your own private node, then you can use whatever name you want for each worker, and it'll all go to the same address. If it's a public node, it's not quite so simple. M
|
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me!
|
|
|
abdullahadam
|
|
July 14, 2014, 10:21:25 PM |
|
My M's Pool Monitor can do the monitoring/alerting for you. (see sig)
If you're using your own private node, then you can use whatever name you want for each worker, and it'll all go to the same address.
If it's a public node, it's not quite so simple.
M
Hmm.. Yes, I am using public nodes. I'll have to figure something out I may have to join a pool that lists the hash rates publicly like http://61.219.119.37:9332/static/dashboard/miner.html?id=1Fgn9Q9GiV6QtuNegAog1wYpWXDAkt1z6o and use kimonifyto create an API for me out of it Thanks
|
|
|
|
|
mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
July 15, 2014, 12:15:31 AM |
|
My M's Pool Monitor can do the monitoring/alerting for you. (see sig)
If you're using your own private node, then you can use whatever name you want for each worker, and it'll all go to the same address.
If it's a public node, it's not quite so simple.
M
Hmm.. Yes, I am using public nodes. I'll have to figure something out I may have to join a pool that lists the hash rates publicly like http://61.219.119.37:9332/static/dashboard/miner.html?id=1Fgn9Q9GiV6QtuNegAog1wYpWXDAkt1z6o and use kimonifyto create an API for me out of it Thanks All nodes should list miner hashrates. The simple solution is to use a different address for each miner. M
|
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me!
|
|
|
bryonp
Member
Offline
Activity: 85
Merit: 10
|
|
July 15, 2014, 01:40:11 AM |
|
And I thank you as I always use your pages for that info on myself!!!
|
|
|
|
abdullahadam
|
|
July 15, 2014, 03:35:43 AM |
|
awesome, thanks. will give it a try
|
|
|
|
norgan
|
|
July 15, 2014, 09:41:18 AM |
|
Over 1Ph/s!
|
|
|
|
jonnybravo0311
Legendary
Offline
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
|
|
July 15, 2014, 12:13:40 PM |
|
Over 1Ph/s!
We've been flirting with the 1PH/s rate over the past week. I've seen it go up to 1.1PH/s, then down to 450TH/s. Right now, I show 743TH/s. What really needs to happen is that the pool rate drops to like 50TH/s... the share difficulty drops to like 250k... I get about 1000 shares... then we shoot up to 2PH/s and solve 10 blocks in a row
|
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.
|
|
|
norgan
|
|
July 15, 2014, 12:16:58 PM |
|
Over 1Ph/s!
We've been flirting with the 1PH/s rate over the past week. I've seen it go up to 1.1PH/s, then down to 450TH/s. Right now, I show 743TH/s. What really needs to happen is that the pool rate drops to like 50TH/s... the share difficulty drops to like 250k... I get about 1000 shares... then we shoot up to 2PH/s and solve 10 blocks in a row Haha but the value of each share is adjusted anyway when that happens right?
|
|
|
|
jonnybravo0311
Legendary
Offline
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
|
|
July 15, 2014, 12:49:35 PM |
|
Over 1Ph/s!
We've been flirting with the 1PH/s rate over the past week. I've seen it go up to 1.1PH/s, then down to 450TH/s. Right now, I show 743TH/s. What really needs to happen is that the pool rate drops to like 50TH/s... the share difficulty drops to like 250k... I get about 1000 shares... then we shoot up to 2PH/s and solve 10 blocks in a row Haha but the value of each share is adjusted anyway when that happens right? Yeah... The shares are weighted. It would be much better to find above average number of shares at the current difficulty.
|
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.
|
|
|
abdullahadam
|
|
July 15, 2014, 09:33:08 PM |
|
Someone explain this to me please P2pool Luck Thirty Days 142.57% according to http://minefast.coincadence.com/p2pool-stats.phpDoes this mean on average you would have earned around 50% more on this pool than on say btcguild (which has 95.209% average for 30 days)?
|
|
|
|
abdullahadam
|
|
July 15, 2014, 09:39:36 PM |
|
Is this also what BTCGuild is reporting?
|
|
|
|
mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
July 15, 2014, 09:40:43 PM |
|
Someone explain this to me please P2pool Luck Thirty Days 142.57% according to http://minefast.coincadence.com/p2pool-stats.phpDoes this mean on average you would have earned around 50% more on this pool than on say btcguild (which has 95.209% average for 30 days)? Every pool has variance. Right now p2pool appears to be on the positive side of luck. That said, I'm not sure this number is right. According to http://p2pool.info/, it's 127.4%. M
|
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me!
|
|
|
abdullahadam
|
|
July 15, 2014, 09:42:43 PM |
|
Every pool has variance. Right now p2pool appears to be on the positive side of luck. That said, I'm not sure this number is right. According to http://p2pool.info/, it's 127.4%. M You are right. I pm'd windpath about this. It's off by 20% or so from p2pool.info
|
|
|
|
|
mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
July 15, 2014, 11:39:21 PM |
|
There are all sorts of things that can affect expected payout. One is luck. Another is how long that user has been here. If both users are past the 3 day PPLNS period, then the numbers are probably caused by luck, but could also be an error on the website. M
|
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me!
|
|
|
jedimstr
|
|
July 15, 2014, 11:42:52 PM |
|
There are all sorts of things that can affect expected payout. One is luck. Another is how long that user has been here. If both users are past the 3 day PPLNS period, then the numbers are probably caused by luck, but could also be an error on the website. M Another possibility is that the "smaller" miner is actually spread across multiple nodes with the same address. I do that with rigs pointed at my personal node in the US or ones in EU or Asia depending depending on lowest latency and distance. Also failover nodes factor in too. So 1TH may not actually be just 1TH, but instead just 1TH on Coincadence.
|
|
|
|
abdullahadam
|
|
July 15, 2014, 11:44:22 PM |
|
Sorry what is this 3 day PPLNS period? Is that how p2pool works?
|
|
|
|
windpath
Legendary
Offline
Activity: 1258
Merit: 1027
|
|
July 15, 2014, 11:56:08 PM |
|
Every pool has variance. Right now p2pool appears to be on the positive side of luck. That said, I'm not sure this number is right. According to http://p2pool.info/, it's 127.4%. M You are right. I pm'd windpath about this. It's off by 20% or so from p2pool.info Hey guys, I did post the formula I'm using earlier to have someone take a look at it... No one gave any feedback. Here is another shot with the source that calculates 30 day luck: I store blocks as they are found, hashrate is collected every minute, I added some comments to explain what numbers are being used... function getThirtyDayLuck($crud, $diff) { // get 30 day average time between blocks $blocks_query = $crud->rawSelect("SELECT COUNT(*) FROM found_blocks WHERE time > DATE_SUB(NOW(), INTERVAL 30 DAY) ORDER BY time DESC"); $blocks = $blocks_query->fetch(PDO::FETCH_ASSOC); $block_count = $blocks['COUNT(*)']; $avg_elapsed_seconds = 2592000 / $block_count; // 2592000 seconds = 30 days // get 30 day hashrate average $hash_query = $crud->rawSelect("SELECT AVG(global_rate) FROM pool_stats WHERE id > DATE_SUB(NOW(), INTERVAL 30 DAY)"); $hash_avg = $hash_query->fetch(PDO::FETCH_ASSOC); $hashrate = $hash_avg['AVG(global_rate)']; // 30 day expected time to block // Difficulty * 2**32 / hashrate = expected number of seconds to find a block $thirty_day_expected = round($diff * pow(2, 32) / $hashrate); // Get luck as % return percentage($thirty_day_expected, $avg_elapsed_seconds, '2')."%"; }
I'm relatively certain this is accurate, but am open to any suggestion as always....
|
|
|
|
mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
July 16, 2014, 12:33:14 AM |
|
Hey guys, I did post the formula I'm using earlier to have someone take a look at it... No one gave any feedback.
You're right. I glossed over it, as it didn't look immediately decipherable to me. Looking at it now.. Here is another shot with the source that calculates 30 day luck: I store blocks as they are found, hashrate is collected every minute, I added some comments to explain what numbers are being used... function getThirtyDayLuck($crud, $diff) { // get 30 day average time between blocks $blocks_query = $crud->rawSelect("SELECT COUNT(*) FROM found_blocks WHERE time > DATE_SUB(NOW(), INTERVAL 30 DAY) ORDER BY time DESC"); $blocks = $blocks_query->fetch(PDO::FETCH_ASSOC); $block_count = $blocks['COUNT(*)']; $avg_elapsed_seconds = 2592000 / $block_count; // 2592000 seconds = 30 days // get 30 day hashrate average $hash_query = $crud->rawSelect("SELECT AVG(global_rate) FROM pool_stats WHERE id > DATE_SUB(NOW(), INTERVAL 30 DAY)"); $hash_avg = $hash_query->fetch(PDO::FETCH_ASSOC); $hashrate = $hash_avg['AVG(global_rate)']; // 30 day expected time to block // Difficulty * 2**32 / hashrate = expected number of seconds to find a block $thirty_day_expected = round($diff * pow(2, 32) / $hashrate); // Get luck as % return percentage($thirty_day_expected, $avg_elapsed_seconds, '2')."%"; }
I'm relatively certain this is accurate, but am open to any suggestion as always.... The immediate problem that jumps out at me is the difficulty changes at least twice a month, closer to three. You need to store some value for each block as it happens, and then calculate it across your range when you display it. This is what I do for Eligius: For each block, store: - average solve time - actual solve time - timestamp of the block then some SQL: for last 10 blocks: SELECT sum(AvgSolveTime) / sum(ActualSolveTime) FROM Luck where Height >= (select min(Height) from (SELECT top 10 Height from Luck where Height <> 0 order by blocktimestamp desc)); for last 12 hours: Select Sum(Luck.AvgSolveTime) / Sum(Luck.ActualSolveTime) FROM Luck Where BlockTimeStamp > (Now - 12 hours); And so forth. You can see the code in github for M's Pool Monitor. M EDIT: Then do a sanity check against a presumably known good source, like p2pool.info.
|
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me!
|
|
|
|