How about the fact that the cgminer dev said should use at least 1 not zero?
M
Yeah, ck said he recommended a setting of 1 - that's why I used it to start with, but as you can see, setting it to 0 works better for my setup
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 311. (Read 2591971 times)
August 14, 2014, 05:53:15 PM
How about the fact that the cgminer dev said should use at least 1 not zero?
M
Yeah, ck said he recommended a setting of 1 - that's why I used it to start with, but as you can see, setting it to 0 works better for my setup
August 14, 2014, 05:15:54 PM
Quote
Generally Bitcoin with some merged alt coins. However the difference between his 13.4 release and the latest head is nearly 8 months of development inactivity.
August 14, 2014, 05:13:44 PM
I've ordered from batch 1, batch 4 and batch 5. Even in batch 5 the issues remain, although I did get "lucky" as one of my batch 5 units actually hashes at 504GH/s stable.
I also have one of those lucky ones at 505Gh/s from B1 - it's the most stable one out the lot!!
Following up from this, I've been experimenting a little more with my settings & here's a screen of the results:
(click for larger)
This is 4 x S3's running at various clock speeds. Looking at the graph, I was running --queue 1 up until ~3am (yup, I'm a night time fiddler
) before changing the setting to --queue 0 & letting them run for the same amount of time. It can clearly be seen that after changing the setting to --queue 0, the DOA rate dropped & smoothed out - this was also confirmed by my nodes info page. Average hash rate was slightly higher as a result, so I'll be keeping all my S3's running with the --queue 0 setting from now on. I'm not saying that this will work for everyone, but it's definitely good for my setup & worth giving a try if you're experiencing a higher than expected DOA rate.The dip in hash rate at the end of the graph was due to a reboot after updating Xubuntu.
Smoke'em if ya got'em
Edit: It's also worth mentioning that my reject rate was at ~4% with --queue 1 - and ~2% with the 0 setting. This is running on a local node.
How about the fact that the cgminer dev said should use at least 1 not zero?
M
August 14, 2014, 04:15:54 PM
Hi guys bit of a noob question. I've got version 13.4 of the pool software. That's the last release on Github. Is that the version that is considered "best?" or is there another build that I should be running. Just asking because I notice that a lot of pools are running different builds.
If your only mining BTC that is the build you want (https://github.com/forrestv/p2pool), if you are looking for some more exotic coins Rav3nPL's build has many already added (https://github.com/Rav3nPL/p2pool-rav).
Generally Bitcoin with some merged alt coins. However the difference between his 13.4 release and the latest head is nearly 8 months of development. I can't help but think that there must be a release in there that adds significant support/features/performance and is particularly stable. Espeically since when I take a look a the running nodes I find a large variety of versions newer than 13.4
August 14, 2014, 03:45:23 PM
Hi guys bit of a noob question. I've got version 13.4 of the pool software. That's the last release on Github. Is that the version that is considered "best?" or is there another build that I should be running. Just asking because I notice that a lot of pools are running different builds.
If your only mining BTC that is the build you want (https://github.com/forrestv/p2pool), if you are looking for some more exotic coins Rav3nPL's build has many already added (https://github.com/Rav3nPL/p2pool-rav).
August 14, 2014, 02:51:39 PM
Hi guys bit of a noob question. I've got version 13.4 of the pool software. That's the last release on Github. Is that the version that is considered "best?" or is there another build that I should be running. Just asking because I notice that a lot of pools are running different builds.
August 14, 2014, 12:07:42 PM
Seems to me the "3 day pplns" isn't entirely accurate. I believe, it's, as others here have stated, x number of shares on the chain ppls. My payout is decreasing, but I've only been on p2pool for 2 days now.
M
It is 8640 shares. People say 3 days because a share is supposed to be 30 seconds, but just like the BTC network's average block generation times fluctuate, so do the share times in p2pool. It's why difficulty is constantly changing - to accommodate the fluctuations in time-to-share.M
Pool Hashrate: 2222.0 TH/sEstimated Time to Block: 10h 35m Current Round: 1d 21h 49m
Normal???
Normal???
Not normal at all. It's like we are twice as likely to find a block now but we are four times more unfortunate too.
August 14, 2014, 08:24:14 AM
I've ordered from batch 1, batch 4 and batch 5. Even in batch 5 the issues remain, although I did get "lucky" as one of my batch 5 units actually hashes at 504GH/s stable.
I also have one of those lucky ones at 505Gh/s from B1 - it's the most stable one out the lot!!
Following up from this, I've been experimenting a little more with my settings & here's a screen of the results:
(click for larger)
This is 4 x S3's running at various clock speeds. Looking at the graph, I was running --queue 1 up until ~3am (yup, I'm a night time fiddler
) before changing the setting to --queue 0 & letting them run for the same amount of time. It can clearly be seen that after changing the setting to --queue 0, the DOA rate dropped & smoothed out - this was also confirmed by my nodes info page. Average hash rate was slightly higher as a result, so I'll be keeping all my S3's running with the --queue 0 setting from now on. I'm not saying that this will work for everyone, but it's definitely good for my setup & worth giving a try if you're experiencing a higher than expected DOA rate.The dip in hash rate at the end of the graph was due to a reboot after updating Xubuntu.
Smoke'em if ya got'em
Edit: It's also worth mentioning that my reject rate was at ~4% with --queue 1 - and ~2% with the 0 setting. This is running on a local node.
August 14, 2014, 02:53:31 AM
some noob question, where do u guys see the share u found on the nodes static.
i have been mining at http://103.25.203.25:9332/static/ since monday and it shows predicted payout until now, it just disappear, what is going on?
i have been mining at http://103.25.203.25:9332/static/ since monday and it shows predicted payout until now, it just disappear, what is going on?
August 14, 2014, 12:23:07 AM
Pool Hashrate: 2222.0 TH/sEstimated Time to Block: 10h 35m Current Round: 1d 21h 49m
Normal???
Here is a page that will show you the history.Normal???
http://p2pool.info/
see if it helps.
by now we should have had at least 3 or 4 blocks..........
August 13, 2014, 11:53:03 PM
Pool Hashrate: 2222.0 TH/sEstimated Time to Block: 10h 35m Current Round: 1d 21h 49m
Normal???
Normal???
Not normal at all. It's like we are twice as likely to find a block now but we are four times more unfortunate too.
August 13, 2014, 11:36:47 PM
Pool Hashrate: 2222.0 TH/sEstimated Time to Block: 10h 35m Current Round: 1d 21h 49m
Normal???
Normal???
August 13, 2014, 07:18:22 PM
p2coins.com:9332 has 81% effie 
Very bad node.
Very bad node.
Has been over 100% consistently till I restarted node recently and had a few mad 25Ths miners on. It will recover
August 13, 2014, 05:22:05 PM
Pool hash rate just shot up to 2.75Ph/s, so every ones income just dropped..........let's hope it brings in more blocks 
Swings & roundabouts.......
Edit: By the way, I just ordered 2 of the new S3+'s - hoping they work as well as the S3's on p2pool. Nice that I could use the refund coupons from the earlier S3's with the order too - fair play to Bitmain
Swings & roundabouts.......
Edit: By the way, I just ordered 2 of the new S3+'s - hoping they work as well as the S3's on p2pool. Nice that I could use the refund coupons from the earlier S3's with the order too - fair play to Bitmain
August 13, 2014, 05:16:53 PM
Seems to me the "3 day pplns" isn't entirely accurate. I believe, it's, as others here have stated, x number of shares on the chain ppls. My payout is decreasing, but I've only been on p2pool for 2 days now.
M
M
August 13, 2014, 05:02:04 PM
Effie is calculated vs pool.
So if pool have 10% DOA/orphan shares and you have locally 10% too, it means you have 100% effie.
If you have 80% it means, that you are 20% under pool average.
So if pool have 10% DOA/orphan shares and you have locally 10% too, it means you have 100% effie.
If you have 80% it means, that you are 20% under pool average.
August 13, 2014, 03:35:35 PM
Efficiency - how is it calculated? And, how much does it matter?
So I'm seeing my efficiency numbers jump all over the place on my node. I've been at 200 shares / 18 orphaned / 6 dead for a little while, but I've seen my efficiency bounce as high as 109% and down to 98%, without the number of shares changing.
Do I assume correctly that the number changes based upon node hashrate, DOA rate, etc as well as the share numbers?
And, how much does it matter that it's bouncing between those numbers? Should I be concerned with the fluctuation, or should I just be concerned if it drops below a certain number and stays there?
So I'm seeing my efficiency numbers jump all over the place on my node. I've been at 200 shares / 18 orphaned / 6 dead for a little while, but I've seen my efficiency bounce as high as 109% and down to 98%, without the number of shares changing.
Do I assume correctly that the number changes based upon node hashrate, DOA rate, etc as well as the share numbers?
And, how much does it matter that it's bouncing between those numbers? Should I be concerned with the fluctuation, or should I just be concerned if it drops below a certain number and stays there?
I believe efficiency is based entirely on how well your node is doing on accepted vs rejected (orphan/stale) shares compared to the entire pool. Odds are it's not your node that's fluctuating, it's the pool.
100% or better is good. That, of course means someone else out there isn't doing so good.
M
August 13, 2014, 03:14:43 PM
Efficiency - how is it calculated? And, how much does it matter?
So I'm seeing my efficiency numbers jump all over the place on my node. I've been at 200 shares / 18 orphaned / 6 dead for a little while, but I've seen my efficiency bounce as high as 109% and down to 98%, without the number of shares changing.
Do I assume correctly that the number changes based upon node hashrate, DOA rate, etc as well as the share numbers?
And, how much does it matter that it's bouncing between those numbers? Should I be concerned with the fluctuation, or should I just be concerned if it drops below a certain number and stays there?
So I'm seeing my efficiency numbers jump all over the place on my node. I've been at 200 shares / 18 orphaned / 6 dead for a little while, but I've seen my efficiency bounce as high as 109% and down to 98%, without the number of shares changing.
Do I assume correctly that the number changes based upon node hashrate, DOA rate, etc as well as the share numbers?
And, how much does it matter that it's bouncing between those numbers? Should I be concerned with the fluctuation, or should I just be concerned if it drops below a certain number and stays there?
August 13, 2014, 12:55:46 PM
http://miner-control.de
P2Pool for
Bitcoin
Litecoin
Anoncoin
Darkcoin
and when you need more
Write me a message August 13, 2014, 12:29:17 PM
Difficulty is very high. It's hard to get a share in with 1.5TH/s. It took me 12 hours to get one share with 1.1 TH/s.
Remember the 3 days PPLNS. Your payout dropped because some of your shares from 3+ days ago have fallen off.
M
in other words at this time isn't profittable mining in p2p with <1.5 TH / s?
E
Jump to: