[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 398.

serje

legendary

Activity: 1232

Merit: 1002

Quote from: bitpop on May 01, 2014, 02:22:02 AM

Quote from: serje on May 01, 2014, 02:14:58 AM

what is the port to mine on http://p2pool.info/ Huh

thanks

9332

80 May also work

with 9332

Code:

[2014-05-01 12:02:17] Pool: 0 URL: http://p2pool.info/:9332 User: 19C7ocZsUu7
SWtFc2zDTh5CAze88b6i73W Password:
[2014-05-01 12:02:17] Press any key to exit, or BFGMiner will try again in 15s.

[2014-05-01 12:02:35] Pool 0 slow/down or URL or credentials invalid
[2014-05-01 12:02:36] No servers were found that could be used to get work from
.
[2014-05-01 12:02:36] Please check the details from the list below of the serve
rs you have input
[2014-05-01 12:02:36] Most likely you have input the wrong URL, forgotten to ad
d a port, or have not set up workers
[2014-05-01 12:02:36] Pool: 0 URL: http://p2pool.info/:9332 User: 19C7ocZsUu7
SWtFc2zDTh5CAze88b6i73W Password:
[2014-05-01 12:02:36] Press any key to exit, or BFGMiner will try again in 15s.

and with 80

Code:

[2014-05-01 12:06:40] Pool: 0 URL: http://p2pool.info/:80 User: 19C7ocZsUu7SW
tFc2zDTh5CAze88b6i73W Password:
[2014-05-01 12:06:40] Press any key to exit, or BFGMiner will try again in 15s.

[2014-05-01 12:06:57] Pool 0 slow/down or URL or credentials invalid
[2014-05-01 12:06:58] No servers were found that could be used to get work from
.
[2014-05-01 12:06:58] Please check the details from the list below of the serve
rs you have input
[2014-05-01 12:06:58] Most likely you have input the wrong URL, forgotten to ad
d a port, or have not set up workers
[2014-05-01 12:06:58] Pool: 0 URL: http://p2pool.info/:80 User: 19C7ocZsUu7SW
tFc2zDTh5CAze88b6i73W Password:
[2014-05-01 12:06:58] Press any key to exit, or BFGMiner will try again in 15s.

so if anyone has any more ideas let me know Cheesy

bitpop

legendary

Activity: 2912

Merit: 1060

Quote from: serje on May 01, 2014, 02:14:58 AM

what is the port to mine on http://p2pool.info/ Huh

thanks

9332

80 May also work

serje

legendary

Activity: 1232

Merit: 1002

what is the port to mine on http://p2pool.info/ Huh

thanks

CartmanSPC

legendary

Activity: 1270

Merit: 1000

Quote from: jonnybravo0311 on April 28, 2014, 01:54:39 PM

Quote from: smoothrunnings on April 28, 2014, 01:36:52 PM

Quote from: jonnybravo0311 on April 28, 2014, 01:16:06 PM

Quote from: smoothrunnings on April 28, 2014, 11:47:57 AM

I am seeing huge swings in the predicted payout, which is normally spot on when a payout occurs because I verify it when I look at when I get paid.

My 100GH miner has fallen to .001 while my 180GH/s of miners is .008 to .010 which doesn't make sense for the 100GH/s miner.

I see the global pool is now 485GH/s.

It depends on when the last share was found by your 100GH miner. Expected payout will indeed swing around wildly as hash rates increase/decrease, share difficulties increase/decrease, shares drop off the payout list, etc.

To see what I mean visit p2pool.smoothrunnings.ca:9332

I went to your node and see nothing wrong with the reported numbers. The payouts to each miner are determined by how many shares that miner has submitted in the given timeframe, and the weights associated to those submitted shares. As an example, I have 2 S1s running on my local node. Currently, my expected payouts show one with 0.02 and the other with 0.007. Both have been running for exactly the same time, but one has found more shares than the other.

Why would you not run both S1's with the same payout address? That way their not competing with each other for shares on your node. I know in the long run it doesn't matter but still...

...or even just run each one with a non payout username so that all the shares go to your nodes payout address if you want to track the performance of each one separate.

smoothrunnings

hero member

Activity: 630

Merit: 501

Quote from: SpainCoinDev on April 30, 2014, 05:21:38 AM

New: NewYorkCoin p2pool (this coin is going to relaunch soon!):
https://github.com/NewYorkCoin/p2pool-nyc

NewYorkCoin? Does it have any value? Is it a scrypt or asic based currency?

smoothrunnings

hero member

Activity: 630

Merit: 501

Quote from: PublicP2poolNode on April 29, 2014, 09:42:04 PM

Lovin days where we have 3 blocks in the last 24 hour window like today

Hoping people who have never given p2pool a try will do so now, while the expected block times are sooner than expired shares. I don't love it when earned shares are wasted, that's when I feel like throwing in the towel.

Then we have days like today that help remind me why I like it here, other than the principles behind it which keep me with p2pool in the bad times as well.

This is one thing I have noticed with P2Pool which leads me to suspect there is a bug in it. Sometimes if I stop my P2Pool to do some maintenance on OpenSUSE and start it up later I noticed that I am lucky to get 10 shares a days, were as if I start and stop it randomly afterwards eventually it starts doing 10 shares day like it's doing right now; this is why it leads me to believe there is some kind of bug in the core of P2Pool because technically this shouldn't happen period.

SpainCoinDev

sr. member

Activity: 364

Merit: 250

SpainCoin.org

New: NewYorkCoin p2pool (this coin is going to relaunch soon!):
https://github.com/NewYorkCoin/p2pool-nyc

PublicP2poolNode

sr. member

Activity: 347

Merit: 252

Lovin days where we have 3 blocks in the last 24 hour window like today

Hoping people who have never given p2pool a try will do so now, while the expected block times are sooner than expired shares. I don't love it when earned shares are wasted, that's when I feel like throwing in the towel.

Then we have days like today that help remind me why I like it here, other than the principles behind it which keep me with p2pool in the bad times as well.

Meuh6879

legendary

Activity: 1512

Merit: 1012

Quote from: mdude77 on April 27, 2014, 01:11:44 PM

p2pool doesn't really know what the hash rate is. It just does an estimate based on how many shares are being found per time period.

but, with "hour" graph. ... the progression is not chaotic.

http://imageshack.com/a/img836/992/6d5f.jpg

roy7

sr. member

Activity: 434

Merit: 250

Quote from: IYFTech on April 28, 2014, 05:20:09 PM

Roy, I didn't realize it was possible to merge mine UNO - are you using the standard p2pool software?

Thanks

UNO is the primary coin, not the merged coin. I run UNO and BTC nodes.

IYFTech

hero member

Activity: 686

Merit: 500

WANTED: Active dev to fix & re-write p2pool in C

Quote from: roy7 on April 09, 2014, 05:20:39 PM

I merge mine Namecoin on UNO and BTC. That's it so far. Haven't tried United Scrypt, Huntercoin, etc.

Roy, I didn't realize it was possible to merge mine UNO - are you using the standard p2pool software?

Thanks

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

Quote from: smoothrunnings on April 28, 2014, 01:36:52 PM

Quote from: jonnybravo0311 on April 28, 2014, 01:16:06 PM

Quote from: smoothrunnings on April 28, 2014, 11:47:57 AM

I am seeing huge swings in the predicted payout, which is normally spot on when a payout occurs because I verify it when I look at when I get paid.

My 100GH miner has fallen to .001 while my 180GH/s of miners is .008 to .010 which doesn't make sense for the 100GH/s miner.

I see the global pool is now 485GH/s.

It depends on when the last share was found by your 100GH miner. Expected payout will indeed swing around wildly as hash rates increase/decrease, share difficulties increase/decrease, shares drop off the payout list, etc.

To see what I mean visit p2pool.smoothrunnings.ca:9332

I went to your node and see nothing wrong with the reported numbers. The payouts to each miner are determined by how many shares that miner has submitted in the given timeframe, and the weights associated to those submitted shares. As an example, I have 2 S1s running on my local node. Currently, my expected payouts show one with 0.02 and the other with 0.007. Both have been running for exactly the same time, but one has found more shares than the other.

smoothrunnings

hero member

Activity: 630

Merit: 501

Quote from: jonnybravo0311 on April 28, 2014, 01:16:06 PM

Quote from: smoothrunnings on April 28, 2014, 11:47:57 AM

I am seeing huge swings in the predicted payout, which is normally spot on when a payout occurs because I verify it when I look at when I get paid.

My 100GH miner has fallen to .001 while my 180GH/s of miners is .008 to .010 which doesn't make sense for the 100GH/s miner.

I see the global pool is now 485GH/s.

It depends on when the last share was found by your 100GH miner. Expected payout will indeed swing around wildly as hash rates increase/decrease, share difficulties increase/decrease, shares drop off the payout list, etc.

To see what I mean visit p2pool.smoothrunnings.ca:9332

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

Quote from: smoothrunnings on April 28, 2014, 11:47:57 AM

I am seeing huge swings in the predicted payout, which is normally spot on when a payout occurs because I verify it when I look at when I get paid.

My 100GH miner has fallen to .001 while my 180GH/s of miners is .008 to .010 which doesn't make sense for the 100GH/s miner.

I see the global pool is now 485GH/s.

It depends on when the last share was found by your 100GH miner. Expected payout will indeed swing around wildly as hash rates increase/decrease, share difficulties increase/decrease, shares drop off the payout list, etc.

smoothrunnings

hero member

Activity: 630

Merit: 501

I am seeing huge swings in the predicted payout, which is normally spot on when a payout occurs because I verify it when I look at when I get paid.

My 100GH miner has fallen to .001 while my 180GH/s of miners is .008 to .010 which doesn't make sense for the 100GH/s miner.

I see the global pool is now 485GH/s.

jedimstr

hero member

Activity: 798

Merit: 1000

The large swings could also be due to large miners using quota pool settings (like in BFGMiner) to jump between p2pool and other centralized pool. Sorta "have your cake and eat it too" mentality.

IYFTech

hero member

Activity: 686

Merit: 500

WANTED: Active dev to fix & re-write p2pool in C

Indeed, the hash rate swing is massive sometimes - I'm wondering if it's due to this redirect issue other pools are experiencing.....?

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: gyverlb on April 27, 2014, 06:12:57 PM

Quote from: mdude77 on April 27, 2014, 03:36:10 PM

I think we're saying the same thing. What's unknown is the time period involved.

M

I'm not sure, the part I didn't quite understand is :

Quote

Pool share difficulty goes up, shares/time goes down, apparent hashrate decreases. Then pool share difficulty goes down to compensate, shares/time goes up, and apparent hashrate increases.

The pool share difficulty is recomputed every new share (according to my p2pool logs) and is adjusted to match the detected hash rate. Past share difficulty is used to compute the average hash rate, not the current difficulty so changing the current difficulty doesn't affect the detected hash rate. So I don't understand why you say that apparent hashrate decreases or increases according to pool share difficulty.

It was the logical assumption I came to. p2pool doesn't know the pool hashrate, so it has to use something to estimate it. The only thing it can estimate it by is how often shares are submitted (shares/some time period). I realize now the problem with that is how often shares are solved is supposed to be fixed ... the 30 second difficulty adjustment you referred to. So I have to nix that thought.

That said, I have a hard time believing the pool rate really fluctuates as much as it appears to.

M

gyverlb

hero member

Activity: 896

Merit: 1000

Quote from: mdude77 on April 27, 2014, 03:36:10 PM

I think we're saying the same thing. What's unknown is the time period involved.

M

I'm not sure, the part I didn't quite understand is :

Quote

Pool share difficulty goes up, shares/time goes down, apparent hashrate decreases. Then pool share difficulty goes down to compensate, shares/time goes up, and apparent hashrate increases.

The pool share difficulty is recomputed every new share (according to my p2pool logs) and is adjusted to match the detected hash rate. Past share difficulty is used to compute the average hash rate, not the current difficulty so changing the current difficulty doesn't affect the detected hash rate. So I don't understand why you say that apparent hashrate decreases or increases according to pool share difficulty.

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: gyverlb on April 27, 2014, 01:30:57 PM

Quote from: mdude77 on April 27, 2014, 01:11:44 PM

Quote from: jacob019 on April 27, 2014, 01:08:36 PM

Network hash rate is up to 524 TH/s, best I've seen. Expected time to block is down to 15 hours, really great!

I'm operating a 0% fee node on a fast server in Chicago.
http://p2pool.1js.us
Come mine with us!

The hash rate seems to jump around quite a bit. I think I finally understand why. p2pool doesn't really know what the hash rate is. It just does an estimate based on how many shares are being found per time period. Since that varies with pool share difficulty, it keeps swinging around. Pool share difficulty goes up, shares/time goes down, apparent hashrate decreases. Then pool share difficulty goes down to compensate, shares/time goes up, and apparent hashrate increases. Rinse and repeat.

M

This effect could be felt only between 2 shares if the difficulty rose of fell rapidly while the actual network speed went in the other direction. Given that the p2pool share interval is only 30 seconds this effect should be negligible.

The problem is more likely to be simply that the hash rate is an estimation on a time period or a number of shares (which is more or less the same). As a mean value it doesn't reflect the fastest changes. I'm not sure how many shares are used for the current hash rate estimation that's probably not hard to find in the code though...

I think we're saying the same thing. What's unknown is the time period involved.

M

Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 398. (Read 2591964 times)