|
ktbken
|
 |
August 14, 2014, 12:18:22 AM |
|
p2coins.com:9332 has 81% effie  Very bad node. Has been over 100% consistently till I restarted node recently and had a few mad 25Ths miners on. It will recover |
|
|
|
wlz2011
Member
 Offline
Activity: 71
Merit: 10
|
|
August 14, 2014, 04:36:47 AM |
|
Pool Hashrate: 2222.0 TH/sEstimated Time to Block: 10h 35m Current Round: 1d 21h 49m Normal???  |
|
|
|
|
|
contactlight
|
|
August 14, 2014, 04:53:03 AM |
|
Pool Hashrate: 2222.0 TH/sEstimated Time to Block: 10h 35m Current Round: 1d 21h 49m 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. |
|
|
|
|
bryonp
Member
Offline
Activity: 85
Merit: 10
|
|
August 14, 2014, 05: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. http://p2pool.info/see if it helps. by now we should have had at least 3 or 4 blocks.......... |
|
|
|
|
|
yan7181
|
|
August 14, 2014, 07: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? |
|
|
|
|
|
IYFTech
|
|
August 14, 2014, 01:24:14 PM
Last edit: August 14, 2014, 01:41:32 PM by IYFTech |
|
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. |
|
|
|
jonnybravo0311
Legendary
Offline
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
|
|
August 14, 2014, 05: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. Pool Hashrate: 2222.0 TH/sEstimated Time to Block: 10h 35m Current Round: 1d 21h 49m 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. It's absolutely normal. It's called variance. With the current hash rate, the pool *expects* to find a block within a timeframe. There's no guarantee it will do so. You'll notice that the pool found 2 blocks within 4 hours of each other earlier today. |
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.
|
|
|
|
chalbersma
|
|
August 14, 2014, 07: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.
|
|
|
|
|
windpath
Legendary
Offline
Activity: 1258
Merit: 1027
|
|
August 14, 2014, 08: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). |
|
|
|
|
|
chalbersma
|
|
August 14, 2014, 09: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 |
|
|
|
|
mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
August 14, 2014, 10: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 |
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me! |
|
|
windpath
Legendary
Offline
Activity: 1258
Merit: 1027
|
|
August 14, 2014, 10:15:54 PM |
|
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.
|
|
|
|
|
|
IYFTech
|
|
August 14, 2014, 10: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  |
|
|
|
|
IYFTech
|
|
August 14, 2014, 10:54:01 PM |
|
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.
Damn right!! |
|
|
|
|
|
EErik
Newbie
Offline
Activity: 26
Merit: 0
|
|
August 15, 2014, 09:14:15 AM |
|
I'm sorry but I honestly do not understand ... how p2p can be the most profittabile when reward fluctuate under 10 mBtc for 1.5 Th / s? in Eligius pool I take 0.036 btc / day I understand the variance of the reward, but for what I have seen of me and many others who have under 2th / s of hashing power is very inconvenient and this is making the p2p pool for a few miners only. E |
|
|
|
|
|
contactlight
|
|
August 15, 2014, 02:13:08 PM |
|
I'm sorry but I honestly do not understand ... how p2p can be the most profittabile when reward fluctuate under 10 mBtc for 1.5 Th / s? in Eligius pool I take 0.036 btc / day I understand the variance of the reward, but for what I have seen of me and many others who have under 2th / s of hashing power is very inconvenient and this is making the p2p pool for a few miners only. E He has 1.5GH/s, take a look at the graph again.  |
|
|
|
|
|
PatMan
|
|
August 15, 2014, 02:13:21 PM |
|
Patience is required with p2pool - I am using less hashrate than you on a couple of different nodes, sometimes I can go without a share for 12 hours or more - then 2 or 3 shares will appear within 5 minutes of each other. Hash rate & diff is going up on every pool - this is the way of things. Just sit tight - it'll come |
|
|
|
|
yan7181
|
|
August 15, 2014, 02:21:34 PM |
|
hi wlz2011, care to share what is the secret behind?  |
|
|
|
|
|
PatMan
|
|
August 15, 2014, 03:34:33 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 Can confirm that using --queue 0 on my S3's results in less DOA also (also running a local node) |
|
|
|
|
