Bitcoin Forum
December 05, 2016, 12:48:14 AM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 [162] 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2029665 times)
racerguy
Sr. Member
****
Offline Offline

Activity: 271


View Profile
August 12, 2012, 12:56:13 PM
 #3221

I've been averaging 0.126btc/day over the last 37days on p2pool with my 5770, my guess is my avg hashrate is just below 200mhash/s(I game as well sometimes on the 5770).  This is well above 100%pps so I can confirm our recent good luck is real but the p2pool.info stats may be a bit off somehow.

On an unrelated point my 5770 is only 5$ away from paying for itself over those 37 days.
1480898894
Hero Member
*
Offline Offline

Posts: 1480898894

View Profile Personal Message (Offline)

Ignore
1480898894
Reply with quote  #2

1480898894
Report to moderator
1480898894
Hero Member
*
Offline Offline

Posts: 1480898894

View Profile Personal Message (Offline)

Ignore
1480898894
Reply with quote  #2

1480898894
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1480898894
Hero Member
*
Offline Offline

Posts: 1480898894

View Profile Personal Message (Offline)

Ignore
1480898894
Reply with quote  #2

1480898894
Report to moderator
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
August 12, 2012, 01:06:13 PM
 #3222

I've been averaging 0.126btc/day over the last 37days on p2pool with my 5770, my guess is my avg hashrate is just below 200mhash/s(I game as well sometimes on the 5770).  This is well above 100%pps so I can confirm our recent good luck is real but the p2pool.info stats may be a bit off somehow.

On an unrelated point my 5770 is only 5$ away from paying for itself over those 37 days.

We were doing great until the last week.  We went from 3-7 blocks a day average to 1-3 blocks a day average, with lower payout per block. Sad  (Note the p2pool.info stats show great numbers except for the last week.)

I'm going to do a week comparison.  I can now easily split my miners 50/50, so I have 2.6g/h going to ozcoin at 5% donation, and 2.6g/h going to p2pool. 

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
racerguy
Sr. Member
****
Offline Offline

Activity: 271


View Profile
August 12, 2012, 01:28:48 PM
 #3223

I've been averaging 0.126btc/day over the last 37days on p2pool with my 5770, my guess is my avg hashrate is just below 200mhash/s(I game as well sometimes on the 5770).  This is well above 100%pps so I can confirm our recent good luck is real but the p2pool.info stats may be a bit off somehow.

On an unrelated point my 5770 is only 5$ away from paying for itself over those 37 days.

We were doing great until the last week.  We went from 3-7 blocks a day average to 1-3 blocks a day average, with lower payout per block. Sad  (Note the p2pool.info stats show great numbers except for the last week.)

I'm going to do a week comparison.  I can now easily split my miners 50/50, so I have 2.6g/h going to ozcoin at 5% donation, and 2.6g/h going to p2pool. 

M

I don't know for sure but when talking about pools in the 300-500ghash range I don't think 1 week is long enough for luck to even out to a reasonable level(maybe organofcorti knows how long it would take). 
organofcorti
Donator
Legendary
*
Offline Offline

Activity: 1946


Poor impulse control.


View Profile WWW
August 12, 2012, 01:44:21 PM
 #3224

We were doing great until the last week.  We went from 3-7 blocks a day average to 1-3 blocks a day average, with lower payout per block. Sad  (Note the p2pool.info stats show great numbers except for the last week.)
Comparing rounds per day isn't helpful unless you also compare hashrates. And yes, you earned less this week than last because there was even better luck last week. Even comparing your week's earnings with last weeks is tricky unless you have a large hashrate.

I'm going to do a week comparison.  I can now easily split my miners 50/50, so I have 2.6g/h going to ozcoin at 5% donation, and 2.6g/h going to p2pool. 

M

Good idea. But remember, your variance will be a bit higher at p2Pool so make sure you make the comparison over a substantial time period.

I don't know for sure but when talking about pools in the 300-500ghash range I don't think 1 week is long enough for luck to even out to a reasonable level(maybe organofcorti knows how long it would take). 

This too. I hadn't thought of that until racerguy brought it up. If p2pool has 1/4 the hashrate of Ozcoin, you should average your results for p2Pool over four times as long. Even at one week for Ozcoin and 4 weeks for p2Pool, you'd still have at 95% confidence interval of +/- 18%. And which week would you select for averaging at Ozcoin?

Still, it's a great idea mdude77, and getting more "hands on" in this fashion might help you get a feel for the differences between pools. Good luck, and a weekly update on your progress wouldn't go astray on the Weekly Pool Statistics thread.

Bitcoin network and pool analysis 12QxPHEuxDrs7mCyGSx1iVSozTwtquDB3r
follow @oocBlog for new post notifications
twmz
Hero Member
*****
Offline Offline

Activity: 737



View Profile
August 12, 2012, 02:30:11 PM
 #3225

I think there's something wrong with the p2Pool 7 day stats. If you calculate manually, the last 7 days is better than average luck. In fact, there's been better than average luck at p2Pool for the last 6 weeks now. Check the last 7 days for yourself:

Code:
         Timestamp   ActualShares ExpectedShares
1  1344745354.000000  547055.000000 2036671.000000
2  1344740792.000000 9116832.000000 2036671.000000
3  1344649552.000000  134207.000000 2036671.000000
4  1344648269.000000 2121584.000000 2036671.000000
5  1344627801.000000 3184026.000000 2036671.000000
6  1344596756.000000 7983068.000000 2036671.000000
7  1344487657.000000 3886934.000000 2036671.000000
8  1344430970.000000  839057.000000 2036671.000000
9  1344418762.000000 1225598.000000 2036671.000000
10 1344401496.000000  814265.000000 2036671.000000
11 1344389344.000000  395892.000000 2036671.000000
12 1344383399.000000 2019198.000000 2036671.000000
13 1344353201.000000  279105.000000 2036671.000000
14 1344349060.000000 1526951.000000 2036671.000000
15 1344325803.000000  644660.000000 2036671.000000
16 1344315777.000000   35732.000000 2036671.000000
17 1344315245.000000  271678.000000 2036671.000000
18 1344311286.000000 1395283.000000 2036671.000000
19 1344289928.000000 1986950.000000 2036671.000000
20 1344258323.000000  152132.000000 2036671.000000
21 1344256008.000000  815393.000000 2036671.000000
22 1344243762.000000 1675975.000000 2036671.000000


The average round length / difficulty = 0.91. This is better than average.

You didn't include this very long block in your calculation (and p2pool.info did):

Code:
23 1344216828.000000 11306170.000000 2036671.000000

Probably you and p2pool.info just used a different definitions of "last 7 days".  p2pool.info includes rounds based on their end time (the timestamp of when the block was found).  So, the 7 day luck calculation include all blocks that were found in the 604,800 seconds (7 days) since the most recent block was found (not since "now").  

At the time of your post, the most recent block had been found at 1344745354.  So the cuttoff was 1344745354 - 604800 = 1344140554, which means that the long block found at 1344216828 was included in the 7 day range.



Was I helpful?  1TwmzX1wBxNF2qtAJRhdKmi2WyLZ5VHRs
WoT, GPG

Bitrated user: ewal.
organofcorti
Donator
Legendary
*
Offline Offline

Activity: 1946


Poor impulse control.


View Profile WWW
August 12, 2012, 02:36:27 PM
 #3226

I should have thought of that, twmz. Yes, I take "now", subtract 7 days and include only rounds completed in that time. So i missed that stonking great round. Good news is your stats will show a much improved 7 day luck shortly Smiley

Which just goes to show that the 7 day luck isn't something mdude77 shouldn't be basing his mining decisions on just the last weeks rounds - the variance in such a short period of time can be huge.

Bitcoin network and pool analysis 12QxPHEuxDrs7mCyGSx1iVSozTwtquDB3r
follow @oocBlog for new post notifications
Krak
Hero Member
*****
Offline Offline

Activity: 591



View Profile WWW
August 12, 2012, 03:20:58 PM
 #3227

My payout is higher than it should be for 1% of the pool hashpower.  Right now the pool is at 500g/h, I'm at 5 g/h.  That's 1%, so I should get a payout of .5btc.  The last couple days I've been around .6 to .65.  That tells me someone, or a bunch of someones out there aren't getting their fair share of hashes.
Include me in there, I've only found 5 shares in the past 24 hours. Undecided

What you do is take all the "ActualShares" and divide by all the "ExpectedShares", and then take the average (add all the ActualShares/ExpectedShares and divide by the number of rounds, 22 in this case). That average is 0.91. This means that the rounds were 9% shorter than expected which means you solved more blocks for your shares (or it took fewer shares to solve your blocks.)

Round length / D gets smaller with good luck and larger with bad luck, and is what I was referring to. I'm not sure how the luck is calculated on the p2Pool graphs or what it means, exactly.

Anyway, the available stats say the good luck is still rolling for p2Pool. Don't sell it short!
How is that done exactly? Does it count all of the high difficulty shares or does it translate them into difficulty 1 shares?

BTC: 1KrakenLFEFg33A4f6xpwgv3UUoxrLPuGn
organofcorti
Donator
Legendary
*
Offline Offline

Activity: 1946


Poor impulse control.


View Profile WWW
August 12, 2012, 03:43:58 PM
 #3228

How is that done exactly? Does it count all of the high difficulty shares or does it translate them into difficulty 1 shares?

The pool hashrate and round duration are used to estimate the number of difficulty 1 shares.

Bitcoin network and pool analysis 12QxPHEuxDrs7mCyGSx1iVSozTwtquDB3r
follow @oocBlog for new post notifications
randomguy7
Hero Member
*****
Offline Offline

Activity: 528


View Profile
August 12, 2012, 04:23:37 PM
 #3229

My p2pool efficiency is only about 93%, someone has a clue what the reason for this could be?

I run my p2pool instance on a server with 100mbit/s connection, my latency to the server is about 20ms.
My miners are cgminer (with icarus boards) and btcminer (with ztex quads).
I rarely run any downloads on my local link to avoid an increase of latency and thereby stales. I even have qos set up to prefer my miners traffic to the normal web traffic while surfing. But efficiency still sucks hard.
Any ideas what else I could try?
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
August 12, 2012, 04:27:56 PM
 #3230

I should have thought of that, twmz. Yes, I take "now", subtract 7 days and include only rounds completed in that time. So i missed that stonking great round. Good news is your stats will show a much improved 7 day luck shortly Smiley

Which just goes to show that the 7 day luck isn't something mdude77 shouldn't be basing his mining decisions on just the last weeks rounds - the variance in such a short period of time can be huge.

It's not just the stats.  It's the results.  I know past results aren't a guarantee of the future.. but I'm seeing an awful lot of red, literally, because rounds are taking too long.  We used to get more blocks, and higher payouts.  Now it's less blocks, and smaller payouts.  That's a double whammy.

And it all started when the extra 120 g/h was added.

I'm hoping it's a bad streak.. but I have yet to see anyone indicate for sure that we don't have a scaling issue.

Any chance p2pool could be changed to auto adjust the share difficulty to a given miner based on hash rate?  I know I haven't taken the time to figure out what my ideal share difficulty is, and I'm sure I'm not the only one.

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
Krak
Hero Member
*****
Offline Offline

Activity: 591



View Profile WWW
August 12, 2012, 04:31:05 PM
 #3231

My p2pool efficiency is only about 93%, someone has a clue what the reason for this could be?

I run my p2pool instance on a server with 100mbit/s connection, my latency to the server is about 20ms.
My miners are cgminer (with icarus boards) and btcminer (with ztex quads).
I rarely run any downloads on my local link to avoid an increase of latency and thereby stales. I even have qos set up to prefer my miners traffic to the normal web traffic while surfing. But efficiency still sucks hard.
Any ideas what else I could try?
Try setting a cap on your incoming connections with --max-conns. I've noticed that nodes with a lot of incoming connections actually have higher dead/orphan rates than nodes with lower connections (I set my max connections to 5 and I almost always have perfect efficiency).

BTC: 1KrakenLFEFg33A4f6xpwgv3UUoxrLPuGn
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
August 12, 2012, 04:33:45 PM
 #3232

My p2pool efficiency is only about 93%, someone has a clue what the reason for this could be?

I run my p2pool instance on a server with 100mbit/s connection, my latency to the server is about 20ms.
My miners are cgminer (with icarus boards) and btcminer (with ztex quads).
I rarely run any downloads on my local link to avoid an increase of latency and thereby stales. I even have qos set up to prefer my miners traffic to the normal web traffic while surfing. But efficiency still sucks hard.
Any ideas what else I could try?

For efficiency rate to be that low, it means your stale rate is pretty high.  Right?

I run two p2pools, on two different machines, with non standard ports.  I have them linked to each other with "-n".  I have my firewall set to forward both nonstandard ports to the respective pools.  My stale rate is ~5%, which right now gives me ~104% efficiency.   Right now I have 24 connections on one, and 11 on the other (was just restarted a few hours ago).

I've also found if I run p2pool on a machine with only one core (processor), my stale rate increases significantly.

Maybe that'll help.

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
Krak
Hero Member
*****
Offline Offline

Activity: 591



View Profile WWW
August 12, 2012, 04:37:51 PM
 #3233

Any chance p2pool could be changed to auto adjust the share difficulty to a given miner based on hash rate?  I know I haven't taken the time to figure out what my ideal share difficulty is, and I'm sure I'm not the only one.
Take a look here. https://bitcointalk.org/index.php?topic=18313.msg816322#msg816322

BTC: 1KrakenLFEFg33A4f6xpwgv3UUoxrLPuGn
randomguy7
Hero Member
*****
Offline Offline

Activity: 528


View Profile
August 12, 2012, 04:45:03 PM
 #3234

My p2pool efficiency is only about 93%, someone has a clue what the reason for this could be?

I run my p2pool instance on a server with 100mbit/s connection, my latency to the server is about 20ms.
My miners are cgminer (with icarus boards) and btcminer (with ztex quads).
I rarely run any downloads on my local link to avoid an increase of latency and thereby stales. I even have qos set up to prefer my miners traffic to the normal web traffic while surfing. But efficiency still sucks hard.
Any ideas what else I could try?

For efficiency rate to be that low, it means your stale rate is pretty high.  Right?

I run two p2pools, on two different machines, with non standard ports.  I have them linked to each other with "-n".  I have my firewall set to forward both nonstandard ports to the respective pools.  My stale rate is ~5%, which right now gives me ~104% efficiency.   Right now I have 24 connections on one, and 11 on the other (was just restarted a few hours ago).

I've also found if I run p2pool on a machine with only one core (processor), my stale rate increases significantly.

Maybe that'll help.

M

That's interesting, all three boxes (2 dedi servers, and my local miner box) I tried p2pool on had only one cpu core.

My stale rate usually isn't very high (the difficulty 1 shares), but the shares which meet the difficulty of the p2pool share chain have a higher stale rate than the pool average. Doesn't make a lot of sense to me but that are my numbers.
Red Emerald
Hero Member
*****
Offline Offline

Activity: 742



View Profile WWW
August 12, 2012, 09:12:13 PM
 #3235

It's not just the stats.  It's the results.  I know past results aren't a guarantee of the future.. but I'm seeing an awful lot of red, literally, because rounds are taking too long.  We used to get more blocks, and higher payouts.  Now it's less blocks, and smaller payouts.  That's a double whammy.

And it all started when the extra 120 g/h was added.

I'm hoping it's a bad streak.. but I have yet to see anyone indicate for sure that we don't have a scaling issue.

Any chance p2pool could be changed to auto adjust the share difficulty to a given miner based on hash rate?  I know I haven't taken the time to figure out what my ideal share difficulty is, and I'm sure I'm not the only one.

M
+1

It seems like we had our luck problem come up last time when the pool grew from 200 to 300 GH/s.  Maybe there is a scaling issue.

eightbitbandit
Newbie
*
Offline Offline

Activity: 8


View Profile
August 12, 2012, 10:59:18 PM
 #3236

Did the latest update up the ram requirement significantly? I've had oom-killer kill the python process twice in 24hrs. I restarted it again this morning and it's already back up to 350mb. This box only has 1gb total, but it's had no problem running p2pool for weeks uninterrupted before. I finally just put an entry in crontab to restart the thing every 6 hrs.

on my Ubuntu-Server with 4GB Ram  bitcoind use 2.6% and Pyhthon 2.5% Memory

Odd. Our bitcoind's are only off by about 20mb, but my p2pool is using around 200mb more. I'm using the latest git pulls of both (as of yesterday anyway).

This is a Fedora 17 32bit box, if that matters.

Did you patch the Fedora yesterday?

I actually just did a few mins ago, but I haven't rebooted to apply the new kernel yet. According to my yum.log, my last python update was on June 03, to 2.7.3-3. Most of the stuff it pulled down today involved dhclient, perl, and the kernel.

For what it's worth, Fedora patched python on Aug 10th and my ballooning RAM dependencies disappeared. I'm holding steady at about 90mb, which is less than my instance of bitcoind (about 100mb). Just thought I'd drop a note to let others know. It's possible they fixed it earlier, because I updated to 2.7.3-7, vs the 2.7.3-3 I was having problems with. I just had a cron running every six hours that restarted my p2pool instance to keep things in check, heh.
pyramining
Hero Member
*****
Offline Offline

Activity: 501


View Profile
August 12, 2012, 11:04:57 PM
 #3237

If you think that my entry in p2pool is breaking up things, I can move my miners to solo-mining. I'm talking of around 250GH/s.

I joined having in mind to help p2pool to perform better, not to upset people.
rav3n_pl
Legendary
*
Offline Offline

Activity: 1320


Don`t panic! Organize!


View Profile
August 12, 2012, 11:32:50 PM
 #3238

This is odd. My payout was usually mostly around 0.02 to top 0.05 per block when rate was 200-250GH and share diff about 500.
Now pool rate is 400-450GH, share diff about 900 and my payout wend down to 0.007 per block and p2pool.info shows me as 53MH. It is over triple less (not double like it "should").
Something is going terribly wrong when pool rate increased, worst thing is we are not finding much more blocks! I hope it will resolve automagially in next 2-3 days.
Maybe adding optional 10x higher share diff for >1GH pool users? As far I understand payout is calculated from number AND diff of share in chain? Ie share on diff 2000 is worth 2x shares diff 1000? This will decrease "spamming" sharechain by biggest miners.
I`m pretty small miner 190MH tops.

1Rav3nkMayCijuhzcYemMiPYsvcaiwHni  Bitcoin stuff on my OneDrive
My RPC CoinControl for any coin https://bitcointalk.org/index.php?topic=929954
My SatoshDice bot https://bitcointalk.org/index.php?topic=897685
organofcorti
Donator
Legendary
*
Offline Offline

Activity: 1946


Poor impulse control.


View Profile WWW
August 12, 2012, 11:43:19 PM
 #3239

Any chance p2pool could be changed to auto adjust the share difficulty to a given miner based on hash rate?  I know I haven't taken the time to figure out what my ideal share difficulty is, and I'm sure I'm not the only one.

Here's some 95% confidence intervals for daily shares submitted:
1000 shares/day: ~ +/- 6%
500 shares/day: ~ +/- 9%
250 shares/day: ~ +/- 14%
125 shares/day: ~ +/- 17%
60 shares/day: ~ +/- 25%

1. Select a target number of shares to be submitted based on a payout variance you can live with (say 500 shares/day = 9%).
2. Work out the number of difficulty 1 shares you'd submit in a day (at 2.4 Ghps, that would be about 48280 diff 1 shares).
3. Divide number of diff 1 shares by the daily shares selected in step 1. In this example, 48280/500 = 98, so in this case a difficulty of 100 would be a good selection.

I'll post a longer list with better granularity if anyone find this useful.

Bitcoin network and pool analysis 12QxPHEuxDrs7mCyGSx1iVSozTwtquDB3r
follow @oocBlog for new post notifications
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
August 13, 2012, 12:07:43 AM
 #3240

This is odd. My payout was usually mostly around 0.02 to top 0.05 per block when rate was 200-250GH and share diff about 500.
Now pool rate is 400-450GH, share diff about 900 and my payout wend down to 0.007 per block and p2pool.info shows me as 53MH. It is over triple less (not double like it "should").
Something is going terribly wrong when pool rate increased, worst thing is we are not finding much more blocks! I hope it will resolve automagially in next 2-3 days.
Maybe adding optional 10x higher share diff for >1GH pool users? As far I understand payout is calculated from number AND diff of share in chain? Ie share on diff 2000 is worth 2x shares diff 1000? This will decrease "spamming" sharechain by biggest miners.
I`m pretty small miner 190MH tops.

This is my point exactly!!  We're getting less blocks and less payout!

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
Pages: « 1 ... 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 [162] 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 ... 744 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!