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

MissouriMiner

sr. member

Activity: 312

Merit: 250

Quote from: mdude77 on October 19, 2014, 11:16:07 AM

Quote from: MissouriMiner on October 19, 2014, 10:57:55 AM

For the last block found (325976), I received a payment much higher than normal or expected. I'm definitely not complaining. This is great!

But I want to understand why? The payout tab showed the normal expected amount, by my payment was 4x that amount. Anyone know why this could happen?

Edit: To add a bit more info. My P2Pool server and default payout address is a different address. I'm talking about my mining address only.

Usually that means you found the block.

M

Wow! You are right. First time ever. I didn't even notice! lol

2014-10-18 22:43:49.668550 GOT BLOCK FROM MINER! Passing to bitcoind! https://blockchain.info/block/00000000000000001928
73ad7facbe0898a86dc8426702c5bf19e37e7f93380b

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: MissouriMiner on October 19, 2014, 10:57:55 AM

For the last block found (325976), I received a payment much higher than normal or expected. I'm definitely not complaining. This is great!

But I want to understand why? The payout tab showed the normal expected amount, by my payment was 4x that amount. Anyone know why this could happen?

Edit: To add a bit more info. My P2Pool server and default payout address is a different address. I'm talking about my mining address only.

Usually that means you found the block.

M

MissouriMiner

sr. member

Activity: 312

Merit: 250

For the last block found (325976), I received a payment much higher than normal or expected. I'm definitely not complaining. This is great!

But I want to understand why? The payout tab showed the normal expected amount, by my payment was 4x that amount. Anyone know why this could happen?

Edit: To add a bit more info. My P2Pool server and default payout address is a different address. I'm talking about my mining address only.

PatMan

hero member

Activity: 924

Merit: 1000

Watch out for the "Neg-Rep-Dogie-Police".....

Quote from: -ck on October 18, 2014, 08:44:00 AM

Quote from: PatMan on October 18, 2014, 08:43:05 AM

Does removing the queue command completely set it to zero?

1 is the default. Also I edited the previous post to mention submitting stales.

Right, thanks. I've always run mine with the zero value - seems to work the best with p2pool for me Wink

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: MissouriMiner on October 18, 2014, 08:43:41 AM

OK. I tried your new binary and it appears the same. I assume because I'm using the pseudo difficulty as you stated. BTW, I am using "--queue 0 --scan-time 1 --expiry 1", which is the typical recommended settings for p2pool.

Give it time too since the original does not submit stales. Scan time and expiry are irrelevant and recommendations for this stem from the dark ages of getwork mining, not stratum. The difference between queue 1 and zero at thousands of work items per second is nothing but it may slow the device down.

MissouriMiner

sr. member

Activity: 312

Merit: 250

Quote from: PatMan on October 18, 2014, 08:43:05 AM

Quote from: -ck on October 18, 2014, 08:39:27 AM

Quote from: MissouriMiner on October 18, 2014, 08:05:28 AM

The default Bitmain 4.6.1 has been working pretty good for me. I get 1.9 TH/s average. And you have to set pseudo difficulty. It doesn't work properly without it. I haven't tried the latest version from ckolivas that was released within the last 24 hours, but I will try it now.

If you used pseudo difficulty with the existing S4 binary, you have circumvented the bulk of the issues, but there is still some gain with the new binary I provided. Just remove any queue value from the init script since 8192 is a crazy default.

Does removing the queue command completely set it to zero?

No. It will use the default, which is 1. I would set it to 0 for p2pool use, but 1 is good for other pools.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: PatMan on October 18, 2014, 08:43:05 AM

Does removing the queue command completely set it to zero?

1 is the default. Also I edited the previous post to mention submitting stales.

MissouriMiner

sr. member

Activity: 312

Merit: 250

Quote from: -ck on October 18, 2014, 08:39:27 AM

Quote from: MissouriMiner on October 18, 2014, 08:05:28 AM

The default Bitmain 4.6.1 has been working pretty good for me. I get 1.9 TH/s average. And you have to set pseudo difficulty. It doesn't work properly without it. I haven't tried the latest version from ckolivas that was released within the last 24 hours, but I will try it now.

If you used pseudo difficulty with the existing S4 binary, you have circumvented the bulk of the issues, but there is still some gain with the new binary I provided. Just remove any queue value from the init script since 8192 is a crazy default.

OK. I tried your new binary and it appears the same. I assume because I'm using the pseudo difficulty as you stated. BTW, I am using "--queue 0 --scan-time 1 --expiry 1", which is the typical recommended settings for p2pool.

PatMan

hero member

Activity: 924

Merit: 1000

Watch out for the "Neg-Rep-Dogie-Police".....

Quote from: -ck on October 18, 2014, 08:39:27 AM

Quote from: MissouriMiner on October 18, 2014, 08:05:28 AM

The default Bitmain 4.6.1 has been working pretty good for me. I get 1.9 TH/s average. And you have to set pseudo difficulty. It doesn't work properly without it. I haven't tried the latest version from ckolivas that was released within the last 24 hours, but I will try it now.

If you used pseudo difficulty with the existing S4 binary, you have circumvented the bulk of the issues, but there is still some gain with the new binary I provided. Just remove any queue value from the init script since 8192 is a crazy default.

Does removing the queue command completely set it to zero?

MissouriMiner

sr. member

Activity: 312

Merit: 250

Quote from: mdude77 on October 18, 2014, 08:32:47 AM

Quote from: MissouriMiner on October 18, 2014, 08:07:28 AM

Quote from: nreal on October 18, 2014, 03:44:33 AM

Pseudo share doesnt affect in founding block anyotherway than it restarts works everytime that changes, so selecting constant could help abit keeping miner busy. Large miners should use bigger sharedifficulty - that would help poolwide. Like btcaddress+501/100000000, then there should be less 5 s restart times, and big miners earn that way more too. Ckolivas proxy helps keeping miners busy also, I have got very good results with it in p2pool and solo pool, it squeezes juice out of miners, with s3s mindiff and startdiff have to be chosen so that you can see best share..

Last weeks bests with 2th= 2,347,645,293, one ~1,500000000, 537,352,921 .. newer got those kind of results without proxy.

S3:s doesnt show best share with all share diff + 512, 1024, 4096 doesnt show, 500, 4000 ... it shows

nohup ./ckpool -p -A -k> /dev/null 2>&1 &

Wondering how ants would perform if those are turned to diskless nodes and booted with tftp, that way cgminer could be running on some more powerfull machine, i think s2 s3 s4 are suffering constan restarts - the mainoboard doesnt have enough power. And that way I doesnt have to wait new firmware and cgminer...

http://wiki.gentoo.org/wiki/Diskless_nodes

It does matter with the S4, and the S2. The S3 works correctly.

It doesn't work with my S2. Doesn't matter what difficulty I set it to, I lose up to 10% of my hash rate by pointing it to p2pool.

M

True. I should have said, it does work except lose up to 10%. I still use it. Some other brand miners are much worse, so I considered mining at 90% of normal as "working". I know many will disagree. Sorry...

I would then say that the S4 is currently working at only 95% of normal.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: MissouriMiner on October 18, 2014, 08:05:28 AM

The default Bitmain 4.6.1 has been working pretty good for me. I get 1.9 TH/s average. And you have to set pseudo difficulty. It doesn't work properly without it. I haven't tried the latest version from ckolivas that was released within the last 24 hours, but I will try it now.

If you used pseudo difficulty with the existing S4 binary, you have circumvented the bulk of the issues, but there is still some gain with the new binary I provided due to the way stales are handled. Just remove any queue value from the init script since 8192 is a crazy default.

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: MissouriMiner on October 18, 2014, 08:07:28 AM

Quote from: nreal on October 18, 2014, 03:44:33 AM

Pseudo share doesnt affect in founding block anyotherway than it restarts works everytime that changes, so selecting constant could help abit keeping miner busy. Large miners should use bigger sharedifficulty - that would help poolwide. Like btcaddress+501/100000000, then there should be less 5 s restart times, and big miners earn that way more too. Ckolivas proxy helps keeping miners busy also, I have got very good results with it in p2pool and solo pool, it squeezes juice out of miners, with s3s mindiff and startdiff have to be chosen so that you can see best share..

Last weeks bests with 2th= 2,347,645,293, one ~1,500000000, 537,352,921 .. newer got those kind of results without proxy.

S3:s doesnt show best share with all share diff + 512, 1024, 4096 doesnt show, 500, 4000 ... it shows

nohup ./ckpool -p -A -k> /dev/null 2>&1 &

Wondering how ants would perform if those are turned to diskless nodes and booted with tftp, that way cgminer could be running on some more powerfull machine, i think s2 s3 s4 are suffering constan restarts - the mainoboard doesnt have enough power. And that way I doesnt have to wait new firmware and cgminer...

http://wiki.gentoo.org/wiki/Diskless_nodes

It does matter with the S4, and the S2. The S3 works correctly.

It doesn't work with my S2. Doesn't matter what difficulty I set it to, I lose up to 10% of my hash rate by pointing it to p2pool.

M

MissouriMiner

sr. member

Activity: 312

Merit: 250

Quote from: nreal on October 18, 2014, 03:44:33 AM

Pseudo share doesnt affect in founding block anyotherway than it restarts works everytime that changes, so selecting constant could help abit keeping miner busy. Large miners should use bigger sharedifficulty - that would help poolwide. Like btcaddress+501/100000000, then there should be less 5 s restart times, and big miners earn that way more too. Ckolivas proxy helps keeping miners busy also, I have got very good results with it in p2pool and solo pool, it squeezes juice out of miners, with s3s mindiff and startdiff have to be chosen so that you can see best share..

Last weeks bests with 2th= 2,347,645,293, one ~1,500000000, 537,352,921 .. newer got those kind of results without proxy.

S3:s doesnt show best share with all share diff + 512, 1024, 4096 doesnt show, 500, 4000 ... it shows

nohup ./ckpool -p -A -k> /dev/null 2>&1 &

Wondering how ants would perform if those are turned to diskless nodes and booted with tftp, that way cgminer could be running on some more powerfull machine, i think s2 s3 s4 are suffering constan restarts - the mainoboard doesnt have enough power. And that way I doesnt have to wait new firmware and cgminer...

http://wiki.gentoo.org/wiki/Diskless_nodes

It does matter with the S4, and the S2. The S3 works correctly.

MissouriMiner

sr. member

Activity: 312

Merit: 250

Quote from: PatMan on October 18, 2014, 06:20:19 AM

Quote from: MissouriMiner on October 17, 2014, 12:21:52 PM

Do you have a recommended optimal setting for the S4? I am using +2048, and it seems to be working OK. What are other S4 owners using for pseudo difficulty?

Did you manage to get the S4 working with p2pool? I saw the test results when Bitmain tried it with IYFTech's node & they were terrible, are you using the latest code from ckolivas? Any improvement?

Peace

The default Bitmain 4.6.1 has been working pretty good for me. I get 1.9 TH/s average. And you have to set pseudo difficulty. It doesn't work properly without it. I haven't tried the latest version from ckolivas that was released within the last 24 hours, but I will try it now.

PatMan

hero member

Activity: 924

Merit: 1000

Watch out for the "Neg-Rep-Dogie-Police".....

Quote from: -ck on October 18, 2014, 06:47:15 AM

Quote from: PatMan on October 18, 2014, 06:20:19 AM

Quote from: MissouriMiner on October 17, 2014, 12:21:52 PM

Do you have a recommended optimal setting for the S4? I am using +2048, and it seems to be working OK. What are other S4 owners using for pseudo difficulty?

Did you manage to get the S4 working with p2pool? I saw the test results when Bitmain tried it with IYFTech's node & they were terrible, are you using the latest code from ckolivas? Any improvement?

Peace

My latest binary works a bazillion times better on p2pool.

http://ck.kolivas.org/apps/cgminer/antminer/s4/4.6.1-141018/cgminer

A bazillion? That's impressive....... Wink

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: PatMan on October 18, 2014, 06:20:19 AM

Quote from: MissouriMiner on October 17, 2014, 12:21:52 PM

Do you have a recommended optimal setting for the S4? I am using +2048, and it seems to be working OK. What are other S4 owners using for pseudo difficulty?

Did you manage to get the S4 working with p2pool? I saw the test results when Bitmain tried it with IYFTech's node & they were terrible, are you using the latest code from ckolivas? Any improvement?

Peace

My latest binary works a bazillion times better on p2pool.

http://ck.kolivas.org/apps/cgminer/antminer/s4/4.6.1-141018/cgminer

PatMan

hero member

Activity: 924

Merit: 1000

Watch out for the "Neg-Rep-Dogie-Police".....

Quote from: MissouriMiner on October 17, 2014, 12:21:52 PM

Do you have a recommended optimal setting for the S4? I am using +2048, and it seems to be working OK. What are other S4 owners using for pseudo difficulty?

Did you manage to get the S4 working with p2pool? I saw the test results when Bitmain tried it with IYFTech's node & they were terrible, are you using the latest code from ckolivas? Any improvement?

Peace

nreal

full member

Activity: 932

Merit: 100

arcs-chain.com

Pseudo share doesnt affect in founding block anyotherway than it restarts works everytime that changes, so selecting constant could help abit keeping miner busy. Large miners should use bigger sharedifficulty - that would help poolwide. Like btcaddress+501/100000000, then there should be less 5 s restart times, and big miners earn that way more too. Ckolivas proxy helps keeping miners busy also, I have got very good results with it in p2pool and solo pool, it squeezes juice out of miners, with s3s mindiff and startdiff have to be chosen so that you can see best share..

Last weeks bests with 2th= 2,347,645,293, one ~1,500000000, 537,352,921 .. newer got those kind of results without proxy.

S3:s doesnt show best share with all share diff + 512, 1024, 4096 doesnt show, 500, 4000 ... it shows

nohup ./ckpool -p -A -k> /dev/null 2>&1 &

Wondering how ants would perform if those are turned to diskless nodes and booted with tftp, that way cgminer could be running on some more powerfull machine, i think s2 s3 s4 are suffering constan restarts - the mainoboard doesnt have enough power. And that way I doesnt have to wait new firmware and cgminer...

http://wiki.gentoo.org/wiki/Diskless_nodes

MissouriMiner

sr. member

Activity: 312

Merit: 250

Quote from: wlz2011 on September 18, 2014, 05:24:52 AM

请使用正确的难度。
P2POOL，这15天效率很低，
原因：中国矿工约有1.5PH/S，使用了超大的难度（+5120或者更多），
我们及时的更改了错误，目前全部使用大约是难度比例1:1。
P2POOL这些天低效率，我们表示抱歉。
但是我们认识到了最好的难度选择是：选择和矿机算力相等的难度。
当前我们的蚂蚁S3+518（+512，S3不显示BestShare），
1TH/S+1028，

S3+518，平均5秒一个Accepted。

S3+5120，大部分计算都超时，被服务器拒绝，能挖到的Share，但是很难产生块。

希望这些数据能帮助到更多的P2POOL矿工，

使用正确的难度选择。

来自中国的P2POOL爱好者。

百度在线翻译

Please use the correct difficulty.
P2POOL, this 15 days the efficiency is very low,
Reason: the Chinese miners about 1.5PH/S, using the large difficulty (+5120 or more),
We amend the wrong, all currently used is about difficulty ratio 1:1.
P2POOL these days and low efficiency, we apologize.
But we recognize the difficulty of selecting the best: the selection and calculation of force is equal to the difficulty of mining machine.
Our current ant S3+518 (+512, S3 does not display the BestShare),
1TH/S+1028,
S3+518, an average of 5 seconds for a Accepted.
S3+5120, most computing timeout, was rejected by the server, can dig into Share, but it is difficult to produce block.
Hope that these data will help to more P2POOL miners,
The use of the difficulty of choosing the right.
From Chinese P2POOL lovers.
Baidu online translation

Do you have a recommended optimal setting for the S4? I am using +2048, and it seems to be working OK. What are other S4 owners using for pseudo difficulty?

nreal

full member

Activity: 932

Merit: 100

arcs-chain.com

Quote from: PatMan on October 17, 2014, 09:28:41 AM

Please sir, can I have some more?......... Cheesy

Let there be some seconds between please, that last was ~0.6s after discus fish found one..

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