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

[Chupacabras]

And a block! 

I want more!!!   

[1714298900]

1714298900

[1714298900]

1714298900

[1714298900]

1714298900

[yslyung]

And a block! 

more blox ! btw, sometimes i see you online sometimes don't. i mean your pool.

c'mon people come join me @ : *pool been hitting good shares*

Pool : stratum+tcp://captminerp2pool.ddns.net:9332     
Worker : Your BTC Address For Payment     
Password : Anything

[sEpuLchEr]

And a block! 

more blox ! btw, sometimes i see you online sometimes don't. i mean your pool.

c'mon people come join me @ : *pool been hitting good shares*

Pool : stratum+tcp://captminerp2pool.ddns.net:9332     
Worker : Your BTC Address For Payment     
Password : Anything

Yes, I make tweaks here and there and if there is no one besides me mining, I'll make the changes and take the chance to reboot the machine. Due to the way I have it set up, it goes offline for about 30 mins for each reboot :p

[idonothave]

I would like to share my deep doubts about the sense of changing cgminer queue parameter.
I know there are many guys here setting queue to 0, but documentation says there has to be 0+ (nonzero) value, so if You set 0 You set 1.
Bitmain sets default 4096 for S3, 8192 for S4/5 units. Personally I do not see ANY difference in what is set there. Yes, ckolivas has written few times, that probably that number is too high, but he also says, he is not author of a driver. So we have to suppose it is better to set there 1 just because it is default setting of cgminer?
Spondoolies... I do not have any idea what queue value is it using, but probably default, so probably 1. I did not study it too much, but are there the same chips? Probably not.
What the queue is good for?
I have tried mining solo some easy altcoin to see, if it makes difference to use value 1 or 1024. Miner is 100GHs (just two pensil moded blades from S1 connected directly thru cp2101 to the laptop with compiled cgminer 4.7.0). No difference there.
From some time I doubt it makes sense to change queue parameter and I do not change it. Let me know if You have any prove of the fact it should increase efficiency and why You think it is so.

[Chupacabras]

what will be the best configuration for getting more shares?
Im running at 5.6 Th. but i only get 4 to 5 shares a day. my pay rate is at 0.035

the user name on the miners i have them with /2000..
Miners that i have S1,S2,S3,S4
My node is running on Win2k8

Thanks.

why /2000 ? min share diff now is roughly 7-9 million +

maybe posting your config/setup might help

try to optimize your pool by :

having a good internet connection, make sure ports are opened, etc

enough memory/cpu to run the pool ? a SSD perhaps ?

+1 on the setting of queue on the ants

how's the latency ? bitcoin.conf can be edited to helpout a little

how abt the local DOA's & stale rate & Valid/Orphans/Dead shares doing ?

Efficiency 100% & above ?

also a little luck is needed too

more info prolly more answers.

don't mean to be an a*s but by just asking plainly for help there ain't gonna be much answers.

now can we hit some blocks grrrrrrr Super Dry yaiks !

this is what i have in bitcoin.cof

rpcuser = bitcoin
rpcpassword = 1N3misrwjkelr;qlejkwr;qlkwejrq;kl
server = 1
blockmaxsize = 500000
mintxfee = 0.000001
minrelaytxfee = 0.000001
maxconnections = 125

also do you mean that i should have 7000 or 9000 instead of 2000?

default blockmaxsize is already 750000 try that & see or you can go max to 1000000

try raising both tx & relay fee to 0.00001

again max conn is 125 default, you can increase, leave it at default or lower it if you've got connection/bandwidth limitations (if there are limitations, i wont suggest running a pool or maybe you can upgrade it)

the share diff changes all the time, either you can set min diff or slightly above, if it's above it will use the higher but not the lower you've set

happy mining.

tbh, if you're not sure what does those commands do, best is to leave it at defaults. ain't broken don't fix it as the old saying goes but no harm trying.

Again i want to thank all of you here.. My cherry got pop.  I found a block...


Miner Status

Summary
Elapsed   GH/S(5s)   GH/S(avg)       FoundBlocks           LocalWork      Utility      WU                      BestShare
1d28m12s  1,950.82  1,973.81               1                  88,010,293   26.36     27,627.24       125062429760


These are my new numbers... thanks

Pool rate: 1.68PH/s (14% DOA+orphan) Share difficulty: 8060000

Node uptime: 1.9 days Peers: 6 out, 2 in

Local rate: 5.19TH/s (2.6% DOA) Expected time to share: 1.9 hours

Shares: 26 total (1 orphaned, 0 dead) Efficiency: 112.2%

Payout if a block were found NOW: 0.05827971 BTC to xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx. Expected after mining for 24 hours: 0.0769 BTC per block.

Current block value: 25.10895134 BTC Expected time to block: 1.2 days

[jonnybravo0311]

Congratulations on finding your first block!

And, to whoever made the donation to p2pool miners, I thank you very much.

[windpath]

Congratulations on finding your first block!

And, to whoever made the donation to p2pool miners, I thank you very much.

Yes, congrats!

And look, a second donation just came through... Pretty cool!

[jonnybravo0311]

Congratulations on finding your first block!

And, to whoever made the donation to p2pool miners, I thank you very much.

Yes, congrats!

And look, a second donation just came through... Pretty cool!

Again, thanks for the donation whoever is sending them!

[Meuh6879]

question : http://p2pool-nodes.info/ ... it's special nodes of P2Pool system ? I mean, can my IP adress can be display here ? (not a problem, it's displayed too on the direct IP connexion between members of P2Pool ... when you look on the router incoming connexion).

[yslyung]

question : http://p2pool-nodes.info/ ... it's special nodes of P2Pool system ? I mean, can my IP adress can be display here ? (not a problem, it's displayed too on the direct IP connexion between members of P2Pool ... when you look on the router incoming connexion).

http://nodes.p2pool.co/

this is much better

post up yr pool details and you will be listed by the site owner soon.

[IYFTech]

I would like to share my deep doubts about the sense of changing cgminer queue parameter.
I know there are many guys here setting queue to 0, but documentation says there has to be 0+ (nonzero) value, so if You set 0 You set 1.
Bitmain sets default 4096 for S3, 8192 for S4/5 units. Personally I do not see ANY difference in what is set there. Yes, ckolivas has written few times, that probably that number is too high, but he also says, he is not author of a driver. So we have to suppose it is better to set there 1 just because it is default setting of cgminer?
Spondoolies... I do not have any idea what queue value is it using, but probably default, so probably 1. I did not study it too much, but are there the same chips? Probably not.

Deep doubts? I posted the results of queue 0 v queue 1 a while ago here:

https://bitcointalk.org/index.php?topic=18313.msg8348972#msg8348972

It is not a hard & fast rule, as everyone has a different set up & different circumstances - so it's best to try both for a while & check the results. Also, I've only ever found that changing the queue setting to 0 only benefits Bitmain hardware, probably due to the inferior firmware/hardware, as my Spondoolies gear runs fine with the default cgminer queue setting of 1.

It's a case of testing, checking & testing again.....

[idonothave]

I would like to share my deep doubts about the sense of changing cgminer queue parameter.
I know there are many guys here setting queue to 0, but documentation says there has to be 0+ (nonzero) value, so if You set 0 You set 1.
Bitmain sets default 4096 for S3, 8192 for S4/5 units. Personally I do not see ANY difference in what is set there. Yes, ckolivas has written few times, that probably that number is too high, but he also says, he is not author of a driver. So we have to suppose it is better to set there 1 just because it is default setting of cgminer?
Spondoolies... I do not have any idea what queue value is it using, but probably default, so probably 1. I did not study it too much, but are there the same chips? Probably not.

Deep doubts? I posted the results of queue 0 v queue 1 a while ago here:

https://bitcointalk.org/index.php?topic=18313.msg8348972#msg8348972

It is not a hard & fast rule, as everyone has a different set up & different circumstances - so it's best to try both for a while & check the results. Also, I've only ever found that changing the queue setting to 0 only benefits Bitmain hardware, probably due to the inferior firmware/hardware, as my Spondoolies gear runs fine with the default cgminer queue setting of 1.

It's a case of testing, checking & testing again.....

Thank You. It seems clear. Can You please share which firmware/cgminer versions are You using there?

[IYFTech]

I would like to share my deep doubts about the sense of changing cgminer queue parameter.
I know there are many guys here setting queue to 0, but documentation says there has to be 0+ (nonzero) value, so if You set 0 You set 1.
Bitmain sets default 4096 for S3, 8192 for S4/5 units. Personally I do not see ANY difference in what is set there. Yes, ckolivas has written few times, that probably that number is too high, but he also says, he is not author of a driver. So we have to suppose it is better to set there 1 just because it is default setting of cgminer?
Spondoolies... I do not have any idea what queue value is it using, but probably default, so probably 1. I did not study it too much, but are there the same chips? Probably not.

Deep doubts? I posted the results of queue 0 v queue 1 a while ago here:

https://bitcointalk.org/index.php?topic=18313.msg8348972#msg8348972

It is not a hard & fast rule, as everyone has a different set up & different circumstances - so it's best to try both for a while & check the results. Also, I've only ever found that changing the queue setting to 0 only benefits Bitmain hardware, probably due to the inferior firmware/hardware, as my Spondoolies gear runs fine with the default cgminer queue setting of 1.

It's a case of testing, checking & testing again.....

Thank You. It seems clear. Can You please share which firmware/cgminer versions are You using there?

Yeah sure, the test was done using the August 26th firmware (antMiner_S320140826.bin) with ckolivas S3 binary that fixes the stale share submission issue that Bitmain ignored. I found this firmware to be the most stable version for my S3's, & when used with ckolivas's binary they finally performed as they should do with p2pool 

[theseraphgabriel]

I would like to share my deep doubts about the sense of changing cgminer queue parameter.
I know there are many guys here setting queue to 0, but documentation says there has to be 0+ (nonzero) value, so if You set 0 You set 1.
Bitmain sets default 4096 for S3, 8192 for S4/5 units. Personally I do not see ANY difference in what is set there. Yes, ckolivas has written few times, that probably that number is too high, but he also says, he is not author of a driver. So we have to suppose it is better to set there 1 just because it is default setting of cgminer?
Spondoolies... I do not have any idea what queue value is it using, but probably default, so probably 1. I did not study it too much, but are there the same chips? Probably not.

Deep doubts? I posted the results of queue 0 v queue 1 a while ago here:

https://bitcointalk.org/index.php?topic=18313.msg8348972#msg8348972

It is not a hard & fast rule, as everyone has a different set up & different circumstances - so it's best to try both for a while & check the results. Also, I've only ever found that changing the queue setting to 0 only benefits Bitmain hardware, probably due to the inferior firmware/hardware, as my Spondoolies gear runs fine with the default cgminer queue setting of 1.

It's a case of testing, checking & testing again.....

IYFTech so will this fix my p2pool issue as you can see in my images below my S1 works fine and finds share with a BS around 5 million but my S3 has never worked right highest best share in a week was 8 million.

Antminer S1
https://i.imgur.com/hXv9p9g.png


Antminer S3
https://i.imgur.com/k8AHDDh.png

Someone told me it was a "luck" thing but I don't think so having same issues with it on regular pool mining also...
Thank You. It seems clear. Can You please share which firmware/cgminer versions are You using there?

Yeah sure, the test was done using the August 26th firmware (antMiner_S320140826.bin) with ckolivas S3 binary that fixes the stale share submission issue that Bitmain ignored. I found this firmware to be the most stable version for my S3's, & when used with ckolivas's binary they finally performed as they should do with p2pool  

I have that firmware on it now do you have a link to the ckolivas fix???
NVRmind I found link but how is it installed what just SSH in and exchange the cgminer in the S3 for this one?

[IYFTech]

....how is it installed what just SSH in and exchange the cgminer in the S3 for this one?

Steps for installing ck's binary on S3:

SSH in then:

a)  cd /usr/bin
b)  mv cgminer cgminer.bak
c)  wget http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.1-141020/cgminer
d)  chmod +x cgminer
e)  /etc/init.d/cgminer restart  (or simply reboot)

To check cgminer version type:  cgminer-api version

Job done 

[theseraphgabriel]

....how is it installed what just SSH in and exchange the cgminer in the S3 for this one?

Steps for installing ck's binary on S3:

SSH in then:

a)  cd /usr/bin
b)  mv cgminer cgminer.bak
c)  wget http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.1-141020/cgminer
d)  chmod +x cgminer
e)  /etc/init.d/cgminer restart  (or simply reboot)

To check cgminer version type:  cgminer-api version

Job done 

TY will test and get back in 24-48 hrs see if it changes
wish I had a like button

[IYFTech]

TY will test and get back in 24-48 hrs see if it changes
wish I had a like button

Not a bother man. I'd also suggest resetting your bitcoin settings to standard - I never found messing with them helped much with p2pool, in fact it usually made matters worse. The only setting that really helps is lowering the "maxconnection" if you suffer from low bandwidth, everything else runs fine using the default settings.

[jcumins]

I have the latest S3 Firmware installed

Here is the version info.

• => VERSION

[CGMiner] => 4.7.0
   [API] => 3.1
   [Miner] => 7.0.0.3
   [CompileTime] => Sat Jan  3 10:37:47 CST 2015
   [Type] => S3

has the cgminer fix been added t this version.

Does any one know.

[sEpuLchEr]

Forgot to thank the last 2 donators.

Thank you! Much appreciated whoever you are!

[IYFTech]

I have the latest S3 Firmware installed

Here is the version info.

• => VERSION

[CGMiner] => 4.7.0
   [API] => 3.1
   [Miner] => 7.0.0.3
   [CompileTime] => Sat Jan  3 10:37:47 CST 2015
   [Type] => S3

has the cgminer fix been added t this version.

Does any one know.

To my knowledge, the cgminer fork used in bitmain firmware(?) all suffer from the same issue with p2pool - which was why ck kindly compiled the S3 binary.

Nice to see a few more blocks drop in lately