Author

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

legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
Thank you all for fast responds and help. Now im seen some improvement from 0.03 to 0.05 almost 0.06. Now im running @ 5.5 Ths Is that about the right pay?
The actual payout depends on the weight of the share when it was found.  It's easy to calculate how many shares you should expect to find, but remember, the share difficulty is constantly changing.  That means the share weights are constantly changing and the expected time to find a share is also constantly changing.

Let's assume a share difficulty of 10000000.  With your 5.5TH/s, you would expect to find a share every 2.17 hours or so, or about 11 shares a day.
legendary
Activity: 1258
Merit: 1027
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.
Edit: And there is really no need to set diff for your miners. P2Pool does an ok (not excellent) vardiff job.

I disagree with that statement.  Bitmain hardware, which a lot of people use, do not like two things:

1 - frequent work restarts.  p2pool averages a restart every 30 seconds.  setting the queue to 1 significantly helps the issue, but when you compare the results with spondoolie hardware, Bitmain sucks
2 - frequent share difficulty changes.  that's the same as #1 when the difficulty increases, causing "low difficulty" work to be submitted and subsequently rejected

You can fix #2 easily enough by setting a fixed pseudo share difficulty.

M
Thank you all for fast responds and help. Now im seen some improvement from 0.03 to 0.05 almost 0.06. Now im running @ 5.5 Ths Is that about the right pay?

That sounds about right. Keep in mind your expected payout can and will fluctuate based on your share submission luck/variance.

You can always find your miner in the active miners tab and see how your luck is holding:

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

If your hashrate reported here is higher than actual you are currently lucky

If your hashrate is lower than actual you are currently unlucky.

member
Activity: 166
Merit: 10
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.
Edit: And there is really no need to set diff for your miners. P2Pool does an ok (not excellent) vardiff job.

I disagree with that statement.  Bitmain hardware, which a lot of people use, do not like two things:

1 - frequent work restarts.  p2pool averages a restart every 30 seconds.  setting the queue to 1 significantly helps the issue, but when you compare the results with spondoolie hardware, Bitmain sucks
2 - frequent share difficulty changes.  that's the same as #1 when the difficulty increases, causing "low difficulty" work to be submitted and subsequently rejected

You can fix #2 easily enough by setting a fixed pseudo share difficulty.

M
Thank you all for fast responds and help. Now im seen some improvement from 0.03 to 0.05 almost 0.06. Now im running @ 5.5 Ths Is that about the right pay?
legendary
Activity: 1540
Merit: 1001
the current share diff CANNOT be changed by using pseudo share diff (max is 999.98) (it only changes the share diff to the miner not the diff set by  p2pool)

p2pool share diff can be lowered by using the "/"

do correct me if i'm wrong.
Setting "+" has no effect on your payouts at all.  It simply makes the graphs prettier or spikier depending on the value you set.  The smaller the value, the more data points p2pool considers for your miner, the smoother the graph.

In an ideal world this would be true.  But with flaky bitmain hardware, setting the pseudo share difficulty will decrease your rejects, which will/may affect your payout.

M
You're correct, and I should have pointed out that caveat.  Also, for some reason with Bitmain's web UI, if you use a power of 2 for your pseudo difficulty, best share value will always be 0.  However, if you use any other value it works just fine.  Bitmain definitely has some peculiar issues with their hardware, firmware and software.

Bitmain has peculiar issues everywhere!! Smiley

M
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
the current share diff CANNOT be changed by using pseudo share diff (max is 999.98) (it only changes the share diff to the miner not the diff set by  p2pool)

p2pool share diff can be lowered by using the "/"

do correct me if i'm wrong.
Setting "+" has no effect on your payouts at all.  It simply makes the graphs prettier or spikier depending on the value you set.  The smaller the value, the more data points p2pool considers for your miner, the smoother the graph.

In an ideal world this would be true.  But with flaky bitmain hardware, setting the pseudo share difficulty will decrease your rejects, which will/may affect your payout.

M
You're correct, and I should have pointed out that caveat.  Also, for some reason with Bitmain's web UI, if you use a power of 2 for your pseudo difficulty, best share value will always be 0.  However, if you use any other value it works just fine.  Bitmain definitely has some peculiar issues with their hardware, firmware and software.
legendary
Activity: 1540
Merit: 1001
the current share diff CANNOT be changed by using pseudo share diff (max is 999.98) (it only changes the share diff to the miner not the diff set by  p2pool)

p2pool share diff can be lowered by using the "/"

do correct me if i'm wrong.
Setting "+" has no effect on your payouts at all.  It simply makes the graphs prettier or spikier depending on the value you set.  The smaller the value, the more data points p2pool considers for your miner, the smoother the graph.

In an ideal world this would be true.  But with flaky bitmain hardware, setting the pseudo share difficulty will decrease your rejects, which will/may affect your payout.

M
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
the current share diff CANNOT be changed by using pseudo share diff (max is 999.98) (it only changes the share diff to the miner not the diff set by  p2pool)

p2pool share diff can be lowered by using the "/"

do correct me if i'm wrong.
Setting "+" has no effect on your payouts at all.  It simply makes the graphs prettier or spikier depending on the value you set.  The smaller the value, the more data points p2pool considers for your miner, the smoother the graph.

Setting "/" does affect your payout IF you set it to a value higher than the current p2pool share difficulty.  Setting it to 1000 makes no difference.  Setting it to 1000000000 would certainly make a difference.  This parameter tells p2pool, "I don't care what you think the share difficulty to get on the chain should be.  You will use the difficulty I provide and weight any shares I submit accordingly."  Unless you have a miner that could potentially be submitting shares faster than every 30 seconds, there is really no reason to use this parameter.
legendary
Activity: 1500
Merit: 1002
Mine Mine Mine
i
d suggest to buy directly from the manufacturers. highly trusted resellers or members that have proven tack record but i would always get it direct.
legendary
Activity: 1540
Merit: 1001
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.
Edit: And there is really no need to set diff for your miners. P2Pool does an ok (not excellent) vardiff job.

I disagree with that statement.  Bitmain hardware, which a lot of people use, do not like two things:

1 - frequent work restarts.  p2pool averages a restart every 30 seconds.  setting the queue to 1 significantly helps the issue, but when you compare the results with spondoolie hardware, Bitmain sucks
2 - frequent share difficulty changes.  that's the same as #1 when the difficulty increases, causing "low difficulty" work to be submitted and subsequently rejected

You can fix #2 easily enough by setting a fixed pseudo share difficulty.

M
I wanted to get Spondoolie, I was not 100% Sure since everyone talks about Antminers I went with it. I will be buy one to test it out.
Have anyone taking a look at this? https://bitgrade.net/shop/ Just ran it to it. But Im really skeptical about it.

Looks like a scam site to me.

I suggest buying directly from Bitmain.  If you ask around, someone might have a coupon they can give/sell you as well to help the cause.

M
member
Activity: 166
Merit: 10
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.
Edit: And there is really no need to set diff for your miners. P2Pool does an ok (not excellent) vardiff job.

I disagree with that statement.  Bitmain hardware, which a lot of people use, do not like two things:

1 - frequent work restarts.  p2pool averages a restart every 30 seconds.  setting the queue to 1 significantly helps the issue, but when you compare the results with spondoolie hardware, Bitmain sucks
2 - frequent share difficulty changes.  that's the same as #1 when the difficulty increases, causing "low difficulty" work to be submitted and subsequently rejected

You can fix #2 easily enough by setting a fixed pseudo share difficulty.

M
I wanted to get Spondoolie, I was not 100% Sure since everyone talks about Antminers I went with it. I will be buy one to test it out.
Have anyone taking a look at this? https://bitgrade.net/shop/ Just ran it to it. But Im really skeptical about it.
legendary
Activity: 1540
Merit: 1001
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.
Edit: And there is really no need to set diff for your miners. P2Pool does an ok (not excellent) vardiff job.

I disagree with that statement.  Bitmain hardware, which a lot of people use, do not like two things:

1 - frequent work restarts.  p2pool averages a restart every 30 seconds.  setting the queue to 1 significantly helps the issue, but when you compare the results with spondoolie hardware, Bitmain sucks
2 - frequent share difficulty changes.  that's the same as #1 when the difficulty increases, causing "low difficulty" work to be submitted and subsequently rejected

You can fix #2 easily enough by setting a fixed pseudo share difficulty.

M

i'm talking abt the conf cmds not bmt (settings) that keeps on raising their prices $ suckerz yes it's sp's game now !

the current share diff CANNOT be changed by using pseudo share diff (max is 999.98) (it only changes the share diff to the miner not the diff set by  p2pool)

p2pool share diff can be lowered by using the "/"

do correct me if i'm wrong.

I'm not talking about the / command.  I'm talking about the - command to raise the psuedo share difficulty going to the miner.

/ never made sense to me.

M
legendary
Activity: 1500
Merit: 1002
Mine Mine Mine
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.
Edit: And there is really no need to set diff for your miners. P2Pool does an ok (not excellent) vardiff job.

I disagree with that statement.  Bitmain hardware, which a lot of people use, do not like two things:

1 - frequent work restarts.  p2pool averages a restart every 30 seconds.  setting the queue to 1 significantly helps the issue, but when you compare the results with spondoolie hardware, Bitmain sucks
2 - frequent share difficulty changes.  that's the same as #1 when the difficulty increases, causing "low difficulty" work to be submitted and subsequently rejected

You can fix #2 easily enough by setting a fixed pseudo share difficulty.

M

i'm talking abt the conf cmds not bmt (settings) that keeps on raising their prices $ suckerz yes it's sp's game now !

the current share diff CANNOT be changed by using pseudo share diff (max is 999.98) (it only changes the share diff to the miner not the diff set by  p2pool)

p2pool share diff can be lowered by using the "/"

do correct me if i'm wrong.
legendary
Activity: 1540
Merit: 1001
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.
Edit: And there is really no need to set diff for your miners. P2Pool does an ok (not excellent) vardiff job.

I disagree with that statement.  Bitmain hardware, which a lot of people use, do not like two things:

1 - frequent work restarts.  p2pool averages a restart every 30 seconds.  setting the queue to 1 significantly helps the issue, but when you compare the results with spondoolie hardware, Bitmain sucks
2 - frequent share difficulty changes.  that's the same as #1 when the difficulty increases, causing "low difficulty" work to be submitted and subsequently rejected

You can fix #2 easily enough by setting a fixed pseudo share difficulty.

M
legendary
Activity: 1500
Merit: 1002
Mine Mine Mine
Finally!!!!! A block.. man.. that was long

NOT enuff ! want MOARRR Wink Need moar hashPOWAHHH c'mon boys let's beat the crap out of other pools
sr. member
Activity: 248
Merit: 250
Are we there yet?
Finally!!!!! A block.. man.. that was long
sr. member
Activity: 248
Merit: 250
Are we there yet?
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.

Yes. Best not to set anything and leave them at the defaults if you do not know what they do, or you'll end up much worst. Start with minimum in the conf or for p2pool, let it run a few days and you can fine tune later when you're more comfortable. Also, when you do make changes, let it run a few days after any changes to better gauge the performance increase/decrease.

Edit: And there is really no need to set diff for your miners. P2Pool does an ok (not excellent) vardiff job.
sr. member
Activity: 248
Merit: 250
Are we there yet?
Aiyeee... agree on super dry... it's mega dry....

Need... blocks... help...  Cry

 Grin Grin
legendary
Activity: 1500
Merit: 1002
Mine Mine Mine
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 Wink

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 Huh 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.
sr. member
Activity: 312
Merit: 250
I ran it. is this right?


alias: -l not found
root@antMiner11:~# /usr/bin/cgminer-api "setconfig|queue,1"
Reply was 'STATUS=E,When=1422193688,Code=45,Msg=Access denied to 'setconfig' command,Description=cgminer 4.7.0|'
[STATUS] =>
(
   [STATUS] => E
   [When] => 1422193688
  
Code:
 => 45
   [Msg] => Access denied to 'setconfig' command
   [Description] => cgminer 4.7.0

Yes and no. Sad

S1s and S3s are finicky about this.  S2s and S4s should accept the command without a problem.

I don't remember how to get S1s and S3s changed.  Maybe someone else can chime in?

M

With S3's, edits to /etc/init.d/cgminer are saved over power cycle, unlike the S2/S4/C1/S5.  So you can simply add your config changes to the "PARAM=" line, such as api-allow, queue, etc...   

With the S5, there is a new file named /config/user_settings.  The only variable it accepts is queue (so far).   For some reason, I have to go to Miner Configuration in the Web UI and Save again for the changes to save past reboot.  I assume a bug.


member
Activity: 166
Merit: 10
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 Wink

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 Huh 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?
Jump to: