Bitcoin Forum
December 09, 2016, 05:34:12 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 [562] 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2033420 times)
idonothave
Full Member
***
Offline Offline

Activity: 234


View Profile
December 05, 2014, 10:18:43 PM
 #11221

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units
1481304852
Hero Member
*
Offline Offline

Posts: 1481304852

View Profile Personal Message (Offline)

Ignore
1481304852
Reply with quote  #2

1481304852
Report to moderator
1481304852
Hero Member
*
Offline Offline

Posts: 1481304852

View Profile Personal Message (Offline)

Ignore
1481304852
Reply with quote  #2

1481304852
Report to moderator
1481304852
Hero Member
*
Offline Offline

Posts: 1481304852

View Profile Personal Message (Offline)

Ignore
1481304852
Reply with quote  #2

1481304852
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1008


Mine at Jonny's Pool


View Profile WWW
December 06, 2014, 12:24:00 AM
 #11222

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units
That's a known problem with the ants.  If you set the pseudo-share difficulty to something other than a power of 2 the best share will show up properly.

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
PatMan
Hero Member
*****
Offline Offline

Activity: 924


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


View Profile WWW
December 06, 2014, 10:27:13 AM
 #11223

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units
That's a known problem with the ants.  If you set the pseudo-share difficulty to something other than a power of 2 the best share will show up properly.

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

Did you also try changing the --queue setting to 0?

"When one person is deluded it is called insanity - when many people are deluded it is called religion" - Robert M. Pirsig.  I don't want your coins, I want change.
Amazon UK BTC payment service - https://bitcointalk.org/index.php?topic=301229.0 - with FREE delivery!
http://www.ae911truth.org/ - http://rethink911.org/ - http://rememberbuilding7.org/
idonothave
Full Member
***
Offline Offline

Activity: 234


View Profile
December 06, 2014, 10:49:51 AM
 #11224

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units
That's a known problem with the ants.  If you set the pseudo-share difficulty to something other than a power of 2 the best share will show up properly.

anyway I let only BTC address as workername, it seems it is working well
node uptime 22 hours, hp 4.78THs, 8 shares 2 orphan, peers 5 in 7 out, doa 1.41 (1-3), getblc latency 0.152, I did some changes during the period so efficiency can be not accurate
after some time if see it is ok I will probably add namecoin merged mining
why global DOA is so high?
idonothave
Full Member
***
Offline Offline

Activity: 234


View Profile
December 06, 2014, 10:52:07 AM
 #11225

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units
That's a known problem with the ants.  If you set the pseudo-share difficulty to something other than a power of 2 the best share will show up properly.

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

Did you also try changing the --queue setting to 0?

yes, I changed with ants to --queue 0 --expiry 1 --scan-time 1 (exclude S4 where I let original setting --queue 8192)
PatMan
Hero Member
*****
Offline Offline

Activity: 924


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


View Profile WWW
December 06, 2014, 11:07:09 AM
 #11226

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units
That's a known problem with the ants.  If you set the pseudo-share difficulty to something other than a power of 2 the best share will show up properly.

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

Did you also try changing the --queue setting to 0?

yes, I changed with ants to --queue 0 --expiry 1 --scan-time 1 (exclude S4 where I let original setting --queue 8192)

--expiry 1 & --scan-time 1 are obsolete, you don't need them. I recommend using zero queue on all Antminers, including the S4, it will lower your DOA/stale rate.

"When one person is deluded it is called insanity - when many people are deluded it is called religion" - Robert M. Pirsig.  I don't want your coins, I want change.
Amazon UK BTC payment service - https://bitcointalk.org/index.php?topic=301229.0 - with FREE delivery!
http://www.ae911truth.org/ - http://rethink911.org/ - http://rememberbuilding7.org/
idonothave
Full Member
***
Offline Offline

Activity: 234


View Profile
December 06, 2014, 11:16:29 AM
 #11227

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units
That's a known problem with the ants.  If you set the pseudo-share difficulty to something other than a power of 2 the best share will show up properly.

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

Did you also try changing the --queue setting to 0?

yes, I changed with ants to --queue 0 --expiry 1 --scan-time 1 (exclude S4 where I let original setting --queue 8192)

--expiry 1 & --scan-time 1 are obsolete, you don't need them. I recommend using zero queue on all Antminers, including the S4, it will lower your DOA/stale rate.

ok, thank You, I will try it
icio
Jr. Member
*
Offline Offline

Activity: 40


View Profile
December 06, 2014, 07:32:46 PM
 #11228

HI everybody, I'm mining with S2, S3 and S4 in different nodes. Every miner has been upgraded with The last firmware but maintening the original Bitmain's configuration. The address registered is without "+ difficulty value".
The S3 work in a range between 441-453 Gh, S2 993-997 Gh, S4 1980-1990 Gh. Recently I also closed some blocks, receiving 0,5% more. The relationship sharechain/THs is very good, almost always higher than real. For about a month I read about miner change enter "--queque 0" instead of the one programmed by Bitmain. A month that pool statistics are worsening.

Are we sure that the changes proposed here on miner are correct?

Happy mining to everybody  Smiley
windpath
Legendary
*
Online Online

Activity: 938


View Profile WWW
December 06, 2014, 07:52:01 PM
 #11229

HI everybody, I'm mining with S2, S3 and S4 in different nodes. Every miner has been upgraded with The last firmware but maintening the original Bitmain's configuration. The address registered is without "+ difficulty value".
The S3 work in a range between 441-453 Gh, S2 993-997 Gh, S4 1980-1990 Gh. Recently I also closed some blocks, receiving 0,5% more. The relationship sharechain/THs is very good, almost always higher than real. For about a month I read about miner change enter "--queque 0" instead of the one programmed by Bitmain. A month that pool statistics are worsening.

Are we sure that the changes proposed here on miner are correct?

Happy mining to everybody  Smiley

It has been a rough few weeks variance/luck wise.

The one thing I know about luck is that it is bound to change Wink

I have not messed with my queue settings, but I doubt that doing so would produce this bad luck.

The reported hash rate at the pool would have to be affected and I would imagine a miner tweaking their settings would be paying attention to that.

jcumins
Full Member
***
Offline Offline

Activity: 192


View Profile
December 07, 2014, 03:35:52 AM
 #11230

I have seen some very strange activity on my node the past 36 hours.

I have 1 s1 and 2 s2 mining on my node.  And the max rate i can get any miner to mine at is .000240 btc  and thats way low what i have seen over the past for a s2.  I would usually average .025 to .03 btc hash rate.

The s1 at that  slower hash rate makes since to me.  But not on the S2.  This is driving me crazy why it is this way.  My equipment is running 2 quad core xeon processors SSD drive and on a 100 meg fiber circuit in my office. The latency for blockchain.info site is 7ms.  So there defiantly not a bandwidth issue.


Any recommendations would surly be appreciated.  Angry
windpath
Legendary
*
Online Online

Activity: 938


View Profile WWW
December 07, 2014, 04:39:36 AM
 #11231

I have seen some very strange activity on my node the past 36 hours.

I have 1 s1 and 2 s2 mining on my node.  And the max rate i can get any miner to mine at is .000240 btc  and thats way low what i have seen over the past for a s2.  I would usually average .025 to .03 btc hash rate.

The s1 at that  slower hash rate makes since to me.  But not on the S2.  This is driving me crazy why it is this way.  My equipment is running 2 quad core xeon processors SSD drive and on a 100 meg fiber circuit in my office. The latency for blockchain.info site is 7ms.  So there defiantly not a bandwidth issue.


Any recommendations would surly be appreciated.  Angry


Could just be bad luck, providing a node address would be helpful to try and diagnose any problems.

Latency to blockchain.info is completely irrelevant, it's the latency to your p2pool peers that matters.

IYFTech
Hero Member
*****
Offline Offline

Activity: 686


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


View Profile
December 07, 2014, 01:46:32 PM
 #11232


Are we sure that the changes proposed here on miner are correct?


There has been a lot of discussion on this here, I provided a graph that showed the advantages of using --queue 0 on a local node - I have not tested the settings on a remote node. If you do a thread search for "--queue", you will see the findings.

Nice to see the blocks are back at last  Smiley

-- Smiley  Thank you for smoking  Smiley --  If you paid VAT to dogie for items you should read this thread:  https://bitcointalk.org/index.php?topic=1018906.0
jcumins
Full Member
***
Offline Offline

Activity: 192


View Profile
December 08, 2014, 12:22:27 AM
 #11233

Ok I have a question for all you smart people in p2pool land.

In the last 24 - 36 hours my rate per minor has dropped of 90%  IE a 1 TH minor would do about .025 btc rate and now i am getting about .0025 to .0030 rate from the same miner.  I do have each miner using there own address and not all using the same one address,

What are you other nodes doing and how does my numbers compare to you.

Thanks for all your wisdom from the past and now into the future.
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
December 08, 2014, 12:51:34 AM
 #11234

Ok I have a question for all you smart people in p2pool land.

In the last 24 - 36 hours my rate per minor has dropped of 90%  IE a 1 TH minor would do about .025 btc rate and now i am getting about .0025 to .0030 rate from the same miner.  I do have each miner using there own address and not all using the same one address,

What are you other nodes doing and how does my numbers compare to you.

Thanks for all your wisdom from the past and now into the future.

If you do indeed have a 1 TH/s miner, you will experience variance.  That means sometimes you'll do better than "expected", and other times you won't.  Right it appears you're in the "won't" luck.

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1008


Mine at Jonny's Pool


View Profile WWW
December 08, 2014, 01:06:14 AM
 #11235

Ok I have a question for all you smart people in p2pool land.

In the last 24 - 36 hours my rate per minor has dropped of 90%  IE a 1 TH minor would do about .025 btc rate and now i am getting about .0025 to .0030 rate from the same miner.  I do have each miner using there own address and not all using the same one address,

What are you other nodes doing and how does my numbers compare to you.

Thanks for all your wisdom from the past and now into the future.
It all depends on how many shares you have on the chain.  As mdude77 pointed out, sometimes you have more than expected, other times you have fewer than expected.  I've seen my own expected payout drop to a single share before, and have seen it do exactly the opposite.  It's variance and it happens to everyone due to the very nature of mining.

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
jcumins
Full Member
***
Offline Offline

Activity: 192


View Profile
December 08, 2014, 01:12:41 AM
 #11236

My node ip is as follows:

207.105.189.40:9332

Please lety me know what you think is right and what i can do better

thanks
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1008


Mine at Jonny's Pool


View Profile WWW
December 08, 2014, 01:18:18 AM
 #11237

My node ip is as follows:

207.105.189.40:9332

Please lety me know what you think is right and what i can do better

thanks
Well, the first problem is that the node is not accessible.  I can't even ping your IP address, or run a trace route to it.  You sure your node is running? Tongue

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
jcumins
Full Member
***
Offline Offline

Activity: 192


View Profile
December 08, 2014, 01:18:42 AM
 #11238

Thanks so much Jonny

I had no idea it was actually tied to the shares.  I per address.  I have since set each miner to there own address so I  can watch the performance per miner.  And I have been playing with the settings and rebooting alot so the shares are zeroing out on each reboot.  Looks like i just need to let it run for a few days and see how it goes.


Thanks so much.

JC Smiley
jcumins
Full Member
***
Offline Offline

Activity: 192


View Profile
December 08, 2014, 01:21:49 AM
 #11239

Yes the node is running it is behind a goof firewall that I will have to open up ping and trace routes to.

I forgot all about that.  I am connecting to it from a data center about 1000 miles away so i know it is accessible from the public.  I will open the firewall for a few days to pings and trace routes
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1008


Mine at Jonny's Pool


View Profile WWW
December 08, 2014, 01:30:50 AM
 #11240

Thanks so much Jonny

I had no idea it was actually tied to the shares.  I per address.  I have since set each miner to there own address so I  can watch the performance per miner.  And I have been playing with the settings and rebooting alot so the shares are zeroing out on each reboot.  Looks like i just need to let it run for a few days and see how it goes.


Thanks so much.

JC Smiley
It's not tied to the shares you see reported by your miners on their UI... it's tied to the shares you find that are accepted onto the share chain.  Each share must meet at least a certain minimum target difficulty in order to be accepted onto the chain.  As of the writing of this post, that difficulty is 12291862.97.  You stated you've got a 1TH/s miner.  That hash rate, with the current difficulty, translates into an expected time to share of 14.66 hours.  Also keep in mind that once you find a share, it has to be accepted on the chain.  An orphan share is one that you've added to the chain and broadcast to the network, but was rejected because the majority of the nodes already had a longer chain than the one you're broadcasting.  A dead share is one that you found, but your local node rejected it when attempting to add it to the chain because your local copy of the chain was already longer.

As I wrote previously, it's all about variance.  I think a picture is worth a thousand words... so here's one for you:


Here you can clearly see that even though the miner's hash rate has remained consistent, the expected payout line is up and down throughout the past month.

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
Pages: « 1 ... 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 [562] 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 ... 744 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!