Author

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

legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
Don't adjust scan or expiry, they're unhelpful. Don't drop queue lower than 1 on hardware that fast as it can impair its performance.
If you don't explicitly set scan/expiry parameters, what do they default to in cgminer?

EDIT: there are recommendations all over the board (bother literally and figuratively) regarding the best and/or most valuable tweaks to make.  Since you wrote the mining software, and I presume are at least conversationally familiar with Bitmain's hardware, what values would you recommend for the S3?  Should we leave it alone at Bitmain's setting of 4096?  Also, is Bitmain really using version 3.1.2 of cgminer, or have they number versions their own way because they've customized the software?  If yes, do you know the version of cgminer on which they based the one in the S3?

Thanks again!

EDIT2: Rather than just a straight up recommendation, is there some kind of formula to calculate the "best" setting for queue depth with a given hash rate and/or mining hardware?

EDIT3: Sorry!  I'm full of questions this morning... would setting the queue depth values be dependent on not only hash rate, but also the pool itself?  For example, would a miner on p2pool wish to have a value of X with hardware Y, but a miner on BTCGuild would want a value of Z for that same hardware Y.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Don't adjust scan or expiry, they're unhelpful. Don't drop queue lower than 1 on hardware that fast as it can impair its performance.
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
S3s on p2pool... flashed the new firmware this morning and edited the cgminer script to set:
Code:
--queue 0 --expiry 1 --scan-time 1
It is REALLY BAD because you are forcing miner to drop work after 1 sec and get new one.
queue=0 is good idea, but scantime should be at least 10s (P2pool share is every 30s) and expiry to max 30 (but expiry means to drop work in queue).

That's an interesting point, and I probably should have considered the ramifications of setting it so low before just believing what I read as a recommendation.  I'm actually tearing down my S3s today, cleaning them completely of the messy thermal compound Bitmain used and putting AS5 on the chips.  I'll restart them with the updated scan time value of 10.

Thanks for the help.
legendary
Activity: 1361
Merit: 1003
Don`t panic! Organize!
S3s on p2pool... flashed the new firmware this morning and edited the cgminer script to set:
Code:
--queue 0 --expiry 1 --scan-time 1
It is REALLY BAD because you are forcing miner to drop work after 1 sec and get new one.
queue=0 is good idea, but scantime should be at least 10s (P2pool share is every 30s) and expiry to max 30 (but expiry means to drop work in queue).
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
S3s on p2pool... flashed the new firmware this morning and edited the cgminer script to set:
Code:
--queue 0 --expiry 1 --scan-time 1
First S3 hashing happily away at 440:


Second S3 hashing away at 427 (this one absolutely refuses to even hash at stock clocks without a smattering of "x" and "-":


Check out those hardware error rates... it's practically non-existent.
legendary
Activity: 1258
Merit: 1027
Thx.

Where can i see, or show on the page, what the miner needed for a Pool Share. So i can reject the question before they come Wink



With the front end your using its in the right column under "Share Difficulty"
legendary
Activity: 986
Merit: 1027
Miner-Control.de Pooler
Thx.

Where can i see, or show on the page, what the miner needed for a Pool Share. So i can reject the question before they come Wink

legendary
Activity: 1258
Merit: 1027
Hy,

i have run a p2pool on http://miner-control.de

I have test it and make with round about 500 GHs few "node" Shares over 340k
Best Share was 1.55M in my cgminer.

But no Share was counted, what is wrong here? Can anybody Helps?

http://miner-control.de/bitcoin_p2pool/

Minimum share difficulty for the pool is currently ~4MM, you did not have any valid shares yet...

Expected time to share should be somewhere around 12 hours at 500GH/s
legendary
Activity: 986
Merit: 1027
Miner-Control.de Pooler
Hy,

i have run a p2pool on http://miner-control.de

I have test it and make with round about 500 GHs few "node" Shares over 340k
Best Share was 1.55M in my cgminer.

But no Share was counted, what is wrong here? Can anybody Helps?

http://miner-control.de/bitcoin_p2pool/
legendary
Activity: 1540
Merit: 1001
Hey guys.... Curious,
As I am sure we are all seeing,
the hash rate keeps going up and down like a yo-yo.

My question, does this effect our block chances?

Is it bad , good , or indifferent?


I don't think the hash rate is varying *that* much.

There's no way, to my knowledge, that p2pool can know what the true hashrate is.  It has to guess.  It guesses by how quickly shares of a given size are being submitted.  Since that's going to vary by luck, the hashrate going to look like a yo-yo on speed.

M
zvs
legendary
Activity: 1680
Merit: 1000
https://web.archive.org/web/*/nogleg.com
Higher p2pool hash rate will decrease variance for larger miners since they'll always have shares & blocks will come more often.  It'll increase variance for small miners, I really have no clue what that is nowadays, maybe 100ghash?... because sometimes you will have no shares, even if blocks are being found.

I always liked to gamble though, anyway.
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
Hey guys.... Curious,
As I am sure we are all seeing,
the hash rate keeps going up and down like a yo-yo.

My question, does this effect our block chances?

Is it bad , good , or indifferent?

As the hash rate goes up, the expected time to block goes down.  As the hash rate goes down, the expected time to block goes up.  The chances of finding a block remains a constant - every hash has a chance to find one.

Edit: If you find your miner in the active miners tab at the link below you can see your estimated effective hash rate which will help you to get an idea of your luck compared with your actual hash rate:

http://minefast.coincadence.com/p2pool-stats.php

Not sure I get this part. Let's say p2pool doesn't find a block for 7 straight days (I hope I wont jinx it). My estimated effective hashrate goes very very down and I will get my share of the 25 BTC when a block is found based on the tiny effective hashrate right?
Windpath's calculation of effective hash rate is based upon the number of shares on the chain that are yours.  So, assuming you are finding an average number of shares, your effective hash rate would remain pretty constant, and close to your actual value.  When that block is found, you receive the reward based upon the number of shares you've got on the chain.  The block pays the previous 8640 shares (approximately 3 days worth).  So, if a block is found in 7 days, or in 7 seconds, your payout is determined by how many of the 8640 shares are yours.
member
Activity: 85
Merit: 10
Hey guys.... Curious,
As I am sure we are all seeing,
the hash rate keeps going up and down like a yo-yo.

My question, does this effect our block chances?

Is it bad , good , or indifferent?
legendary
Activity: 1258
Merit: 1027
Edit: If you find your miner in the active miners tab at the link below you can see your estimated effective hash rate which will help you to get an idea of your luck compared with your actual hash rate:

http://minefast.coincadence.com/p2pool-stats.php

Not sure I get this part. Let's say p2pool doesn't find a block for 7 straight days (I hope I wont jinx it). My estimated effective hashrate goes very very down and I will get my share of the 25 BTC when a block is found based on the tiny effective hashrate right?

Blocks found by p2pool have no effect on this.

It is relative to your found shares active in the p2pool share chain:

If you are lucky in finding shares your estimated hash rate will be higher.
If you are unlucky in finding shares your estimated hash rate will lower.

legendary
Activity: 1904
Merit: 1007
Edit: If you find your miner in the active miners tab at the link below you can see your estimated effective hash rate which will help you to get an idea of your luck compared with your actual hash rate:

http://minefast.coincadence.com/p2pool-stats.php

Not sure I get this part. Let's say p2pool doesn't find a block for 7 straight days (I hope I wont jinx it). My estimated effective hashrate goes very very down and I will get my share of the 25 BTC when a block is found based on the tiny effective hashrate right?
legendary
Activity: 1258
Merit: 1027
This may have been answered in the past, but I can't keep track of the whole thread so I will ask again.

I'm having 5.5Th/s mining on a p2pool node and my predicted payout is at 0.11. Someone else with 4Th/s at Eligius has a 0.11 payout per day. Eligius is giving me the average number while the p2pool is giving me the "live" payout taking into consideration other factors like luck? Thx.

p2pool and Eligius use 2 completely different payout systems:

Eligius: Capped PPS with Recent Backpay (paid from payout queen)
p2pool: PPLNS (Pay Per Last N Shares) (paid directly from block generation TX)

https://en.bitcoin.it/wiki/Comparison_of_mining_pools

p2pool does not predict a payout, it tells you exactly what your payout would be if a block were found "now".

For p2pool your payout is directly related to the number of active shares you have in the p2pool share chain when a block is found.

The share chain lasts ~3 days, so a share (a representation of a payout amount) is valid for any blocks found in the ~3 days after you find the share.

Finding shares is subject to luck/variance just like finding blocks is.

Edit: If you find your miner in the active miners tab at the link below you can see your estimated effective hash rate which will help you to get an idea of your luck compared with your actual hash rate:

http://minefast.coincadence.com/p2pool-stats.php

legendary
Activity: 1904
Merit: 1007
This may have been answered in the past, but I can't keep track of the whole thread so I will ask again.

I'm having 5.5Th/s mining on a p2pool node and my predicted payout is at 0.11. Someone else with 4Th/s at Eligius has a 0.11 payout per day. Eligius is giving me the average number while the p2pool is giving me the "live" payout taking into consideration other factors like luck? Thx.
legendary
Activity: 1258
Merit: 1027
Bounty Refund - S2 & S3

The bounty I set up for forrestv to come up with a working fix for the Antminer S2 & S3 ends tomorrow with no sign of any work completed.

Fortunately Bitmain came through with the S3, and it is working as expected on p2pool, link below is 4x stock S3 hashing as expected:

http://minefast.coincadence.com/miner.php?id=19vXrwKGUhK4cCU8tA4kWZgbChcmh9a6qj

The S2 still has the same problems it had when the bounty was established.

If you donated to the bounty address please PM me your TX # and the address you would like your refund sent to. If you did not let me know when you donated I may ask you to sign a message from the sending address to prove your identity.

Thanks to those who contributed.

The next bounty will be open to all developers.

The bounty has ended with no work submitted, refunds have been issued for those of you who I had contact with. If you donated and have not contacted me yet please do so ASAP so I can get your refund out to you.

Last night I spent some time with a miner on my node working on support over email - turns out he is mining with an S2 - I'm disappointed to say I had to suggest he switch to another pool.

Perhaps now that Bitmain has the S1 & S3s working with p2pool they will go back and revise the S2 firmware...

sr. member
Activity: 308
Merit: 250
Decentralize your hashing - p2pool - Norgz Pool
I am seeing payouts a little lower but more of them. lately I've been very happy with payouts from p2pool using around 240gh/s. Just echoing above comments that you should not panic because you are seeing lower expected payout, you will still see as much per day on average then you did before.
sr. member
Activity: 397
Merit: 250
Just finished catching up on the S2 issue with p2pool and from what I read it seems this is still not resolved. That is too bad I would love to put the S2's on p2pool.
Jump to: