Bitcoin Forum
December 03, 2016, 11:57:27 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 ... 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 613 614 615 616 617 618 619 620 621 622 623 624 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2029196 times)
Prelude
Legendary
*
Offline Offline

Activity: 1204



View Profile
January 06, 2015, 09:27:19 PM
 #11461

Thanks for the chart. Sucks that they left p2pool, I wonder they did. Gotta figure out a way to get more power on the pool!

more reliable nodes ? spread the word, more support for each other & developments for p2pool

i have 2 myself & helped a buddy to make 1 on his own.

I have been thinking about making my private node public to help out a bit, but I have no idea where to start with that. Are there any guides? Here's what it looks like locally, I've been meaning to ask whether it is performing as well as it should be:





I'd appreciate any feedback on the node's performance. It's running on high end hardware, SSD, and is connect to the internet VIA a 175/175Mbps fiber optic connection.

Thanks for the chart. Sucks that they left p2pool, I wonder they did. Gotta figure out a way to get more power on the pool!

more reliable nodes ? spread the word, more support for each other & developments for p2pool

i have 2 myself & helped a buddy to make 1 on his own.

The current design of p2pool has a fatal flaw.

The more hashpower it has, the higher the share difficulty gets, which knocks out "smaller" miners.
The less it has, the easier it is for smaller miners, but the longer it is from blocks.

Can't have your blocks and miners too.

M

That could be aided by big miners setting higher difficulty shares right?
1480809447
Hero Member
*
Offline Offline

Posts: 1480809447

View Profile Personal Message (Offline)

Ignore
1480809447
Reply with quote  #2

1480809447
Report to moderator
1480809447
Hero Member
*
Offline Offline

Posts: 1480809447

View Profile Personal Message (Offline)

Ignore
1480809447
Reply with quote  #2

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

Posts: 1480809447

View Profile Personal Message (Offline)

Ignore
1480809447
Reply with quote  #2

1480809447
Report to moderator
1480809447
Hero Member
*
Offline Offline

Posts: 1480809447

View Profile Personal Message (Offline)

Ignore
1480809447
Reply with quote  #2

1480809447
Report to moderator
1480809447
Hero Member
*
Offline Offline

Posts: 1480809447

View Profile Personal Message (Offline)

Ignore
1480809447
Reply with quote  #2

1480809447
Report to moderator
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
January 06, 2015, 09:48:00 PM
 #11462

I'd appreciate any feedback on the node's performance. It's running on high end hardware, SSD, and is connect to the internet VIA a 175/175Mbps fiber optic connection.

That looks good to me.

Quote
Quote
The current design of p2pool has a fatal flaw.

The more hashpower it has, the higher the share difficulty gets, which knocks out "smaller" miners.
The less it has, the easier it is for smaller miners, but the longer it is from blocks.

Can't have your blocks and miners too.

M

That could be aided by big miners setting higher difficulty shares right?

It can help with very large miners, yes.  Doesn't seem like there are any right now.

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.
windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
January 06, 2015, 09:48:38 PM
 #11463

Thanks for the chart. Sucks that they left p2pool, I wonder they did. Gotta figure out a way to get more power on the pool!

more reliable nodes ? spread the word, more support for each other & developments for p2pool

i have 2 myself & helped a buddy to make 1 on his own.

I have been thinking about making my private node public to help out a bit, but I have no idea where to start with that. Are there any guides? Here's what it looks like locally, I've been meaning to ask whether it is performing as well as it should be:

...

I'd appreciate any feedback on the node's performance. It's running on high end hardware, SSD, and is connect to the internet VIA a 175/175Mbps fiber optic connection.

Performance looks great, would not mess with it.

To open it up to the public make sure ports 9332 and 9333 are open to the public and map to your p2pool server on your LAN...

The current design of p2pool has a fatal flaw.

The more hashpower it has, the higher the share difficulty gets, which knocks out "smaller" miners.
The less it has, the easier it is for smaller miners, but the longer it is from blocks.

Can't have your blocks and miners too.

M

That could be aided by big miners setting higher difficulty shares right?


There is a minimum amount of hash power to expect a share in each block found, as the pool rate increases so does that minimum power requirement.

Right now I'd estimate around 500 GH/s as a safe minimum based on current active miners with payouts.

If you go to the global stats page, click on the active miners tab and sort by estimated hashrate you can get an idea of the minimum.

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


mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
January 06, 2015, 10:06:25 PM
 #11464

There is a minimum amount of hash power to expect a share in each block found, as the pool rate increases so does that minimum power requirement.

Right now I'd estimate around 500 GH/s as a safe minimum based on current active miners with payouts.

If you go to the global stats page, click on the active miners tab and sort by estimated hashrate you can get an idea of the minimum.

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

I couldn't imagine mining on p2pool with 500 GH/s.  The variance would be horrid.

I've got about 5.7 TH/s on here, and my expected time to share is 2.5 hours.  Working backwards, that's about one share every 28.5 hours on average with 500 GH/s.

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.
windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
January 06, 2015, 10:09:03 PM
 #11465

There is a minimum amount of hash power to expect a share in each block found, as the pool rate increases so does that minimum power requirement.

Right now I'd estimate around 500 GH/s as a safe minimum based on current active miners with payouts.

If you go to the global stats page, click on the active miners tab and sort by estimated hashrate you can get an idea of the minimum.

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

I couldn't imagine mining on p2pool with 500 GH/s.  The variance would be horrid.

I've got about 5.7 TH/s on here, and my expected time to share is 2.5 hours.  Working backwards, that's about one share every 28.5 hours on average with 500 GH/s.

M

Agreed, it would be like a long visit to the dentist waiting for those shares, but you would expect to find one share for each block, here is an example of a miner estimated at ~500GH/s:

http://minefast.coincadence.com/miner.php?id=1LavTqNGUSwS4qHWK1d8ZRNQjCxU3bouYQ


mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
January 06, 2015, 10:10:30 PM
 #11466

There is a minimum amount of hash power to expect a share in each block found, as the pool rate increases so does that minimum power requirement.

Right now I'd estimate around 500 GH/s as a safe minimum based on current active miners with payouts.

If you go to the global stats page, click on the active miners tab and sort by estimated hashrate you can get an idea of the minimum.

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

I couldn't imagine mining on p2pool with 500 GH/s.  The variance would be horrid.

I've got about 5.7 TH/s on here, and my expected time to share is 2.5 hours.  Working backwards, that's about one share every 28.5 hours on average with 500 GH/s.

M

Agreed, it would be like a long visit to the dentist waiting for those shares, but you would expect to find one share for each block, here is an example of a miner estimated at ~500GH/s:

http://minefast.coincadence.com/miner.php?id=1LavTqNGUSwS4qHWK1d8ZRNQjCxU3bouYQ

To each their own!!

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.
Prelude
Legendary
*
Offline Offline

Activity: 1204



View Profile
January 06, 2015, 10:20:33 PM
 #11467

Thanks for the info, guys.

Quote from: windpath
To open it up to the public make sure ports 9332 and 9333 are open to the public and map to your p2pool server on your LAN...

Should 8333 be opened also to provide better node connectivity? I currently have 8333 and 9333 open.

Any security precautions to take into consideration?

Edit: Opened up 9332, and allowed responding to pings.

http://69.157.250.149:9332/static/

Would you fellas mind pinging my server and posting your results? Specifying your general location would be appreciated, too. The server is located in Montreal, Canada.
idonothave
Full Member
***
Offline Offline

Activity: 234


View Profile
January 06, 2015, 10:38:27 PM
 #11468

Thanks for the info, guys.

Quote from: windpath
To open it up to the public make sure ports 9332 and 9333 are open to the public and map to your p2pool server on your LAN...

Should 8333 be opened also to provide better node connectivity? I currently have 8333 and 9333 open.

Any security precautions to take into consideration?

Edit: Opened up 9332, and allowed responding to pings.

http://69.157.250.149:9332/static/

Would you fellas mind pinging my server and posting your results? Specifying your general location would be appreciated, too. The server is located in Montreal, Canada.

what You have is more then good, no need to make any change, imho
windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
January 06, 2015, 10:39:39 PM
 #11469

Thanks for the info, guys.

Quote from: windpath
To open it up to the public make sure ports 9332 and 9333 are open to the public and map to your p2pool server on your LAN...

Should 8333 be opened also to provide better node connectivity? I currently have 8333 and 9333 open.

Any security precautions to take into consideration?

Edit: Opened up 9332, and allowed responding to pings.

http://69.157.250.149:9332/static/

Would you fellas mind pinging my server and posting your results? Specifying your general location would be appreciated, too. The server is located in Montreal, Canada.

Ping from NYC (US east) ~60ms

You can ping yourself from various places here: http://www.pingtest.net/

Prelude
Legendary
*
Offline Offline

Activity: 1204



View Profile
January 06, 2015, 10:57:11 PM
 #11470

Quote from: idonothave
what You have is more then good, no need to make any change, imho

 Cool

Quote from: windpath
Ping from NYC (US east) ~60ms

You can ping yourself from various places here: http://www.pingtest.net/

Thanks for the link. Weird that you're getting 60ms, pinging Brooklyn gets me 25ms.

Added a second dashboard just now, will have to figure out which is best to use and how to customize it to my liking.

http://69.157.250.149:9332/static/p2pool-node-status/
Duce
Full Member
***
Offline Offline

Activity: 155


View Profile
January 07, 2015, 02:21:48 AM
 #11471

Quote from: idonothave
what You have is more then good, no need to make any change, imho

 Cool

Quote from: windpath
Ping from NYC (US east) ~60ms

You can ping yourself from various places here: http://www.pingtest.net/

Thanks for the link. Weird that you're getting 60ms, pinging Brooklyn gets me 25ms.

Added a second dashboard just now, will have to figure out which is best to use and how to customize it to my liking.

http://69.157.250.149:9332/static/p2pool-node-status/
round-trip min/avg/max/stddev = 97.756/101.354/107.775/3.277 ms from Southern California.
Prelude
Legendary
*
Offline Offline

Activity: 1204



View Profile
January 07, 2015, 02:50:27 AM
 #11472

Quote from: idonothave
what You have is more then good, no need to make any change, imho

 Cool

Quote from: windpath
Ping from NYC (US east) ~60ms

You can ping yourself from various places here: http://www.pingtest.net/

Thanks for the link. Weird that you're getting 60ms, pinging Brooklyn gets me 25ms.

Added a second dashboard just now, will have to figure out which is best to use and how to customize it to my liking.

http://69.157.250.149:9332/static/p2pool-node-status/
round-trip min/avg/max/stddev = 97.756/101.354/107.775/3.277 ms from Southern California.

Thanks! That's pretty good considering the distance.
jonnybravo0311
Hero Member
*****
Offline Offline

Activity: 994


Mine at Jonny's Pool


View Profile WWW
January 07, 2015, 03:11:58 AM
 #11473

Thanks for the info, guys.

Quote from: windpath
To open it up to the public make sure ports 9332 and 9333 are open to the public and map to your p2pool server on your LAN...

Should 8333 be opened also to provide better node connectivity? I currently have 8333 and 9333 open.

Any security precautions to take into consideration?

Edit: Opened up 9332, and allowed responding to pings.

http://69.157.250.149:9332/static/

Would you fellas mind pinging my server and posting your results? Specifying your general location would be appreciated, too. The server is located in Montreal, Canada.
I just checked out your node... 5 S4s on it, 4 of which are reporting 2TH/s or greater.  Looks like whatever firmware you're running is working out well on p2pool.  Guess Bitmain finally got around to fixing that, huh? Smiley

I'm traveling for work this week (currently in Cleveland, OH).  Ping to your server from here:
round-trip min/avg/max/stddev = 48.655/56.074/85.242/7.561 ms

Have you checked out Matt's relay network? https://bitcointalk.org/index.php?topic=766190.0

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.
Prelude
Legendary
*
Offline Offline

Activity: 1204



View Profile
January 07, 2015, 03:57:14 AM
 #11474

Thanks for the info, guys.

Quote from: windpath
To open it up to the public make sure ports 9332 and 9333 are open to the public and map to your p2pool server on your LAN...

Should 8333 be opened also to provide better node connectivity? I currently have 8333 and 9333 open.

Any security precautions to take into consideration?

Edit: Opened up 9332, and allowed responding to pings.

http://69.157.250.149:9332/static/

Would you fellas mind pinging my server and posting your results? Specifying your general location would be appreciated, too. The server is located in Montreal, Canada.
I just checked out your node... 5 S4s on it, 4 of which are reporting 2TH/s or greater.  Looks like whatever firmware you're running is working out well on p2pool.  Guess Bitmain finally got around to fixing that, huh? Smiley

I'm traveling for work this week (currently in Cleveland, OH).  Ping to your server from here:
round-trip min/avg/max/stddev = 48.655/56.074/85.242/7.561 ms

Have you checked out Matt's relay network? https://bitcointalk.org/index.php?topic=766190.0

Yep, they work perfectly with p2pool. Bitmain addressed the issue with the firmware they released on Oct. 16th, more or less. For slightly better results, it's best to use ck's firmware found here: https://bitcointalk.org/index.php?topic=796839.msg9242449#msg9242449

That 5th S4 has a half dead hashing board, need to get it RMAed soon. Thanks for the ping results. As for the relay server, I've got that running too. I was expecting it to be complicated to set up, but thankfully it was easy as pie. Smiley


Duce
Full Member
***
Offline Offline

Activity: 155


View Profile
January 07, 2015, 06:05:10 AM
 #11475

Has anybody seen this before? I know P2P is kicking this connection out but I have been getting hit tonight from the same node 14.111.192.xxx but with a different last octet and port though. This is just one example.

Code:
2015-01-06 21:40:27.138214 Incoming connection to peer 14.111.192.252:63478 established. p2pool version: 1300 'e9b4018'

Then it gets kicked out:
Code:
2015-01-06 21:40:42.139539 > in handle_share_hashes:
2015-01-06 21:40:42.139653 > Traceback (most recent call last):
2015-01-06 21:40:42.139700 > Failure: twisted.internet.defer.TimeoutError: in GenericDeferrer
2015-01-06 21:40:42.140333 Lost peer 14.111.192.252:63478 - Connection was aborted locally, using.

I could just go block it I guess but as it is not connected longer than ~30sec not sure if I should bother. Has this happened to anybody here before and I have just been privileged?

EDIT: It looks like they gave up as of this morning.
grn
Sr. Member
****
Offline Offline

Activity: 328


View Profile
January 07, 2015, 06:11:46 AM
 #11476

That screen is localhost - not http://192.168.0.4:9332  Huh

localhost is that ip

How is that Lexical analysis working out bickneleski?
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
January 07, 2015, 10:32:11 AM
 #11477

Yep, they work perfectly with p2pool. Bitmain addressed the issue with the firmware they released on Oct. 16th, more or less. For slightly better results, it's best to use ck's firmware found here: https://bitcointalk.org/index.php?topic=796839.msg9242449#msg9242449

Not sure I'd say perfectly?  The still default to 8192 queue size and large amounts of stales.  I got mine down to about 3.4% stales, which is almost twice as bad as my SP20s at 1.8% stale.

Thanks for the ck firmware link, didn't know about that, will have to try it.

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.
idonothave
Full Member
***
Offline Offline

Activity: 234


View Profile
January 07, 2015, 12:46:40 PM
 #11478

That screen is localhost - not http://192.168.0.4:9332  Huh

localhost is that ip

if both 127.0.0.1:9332 and 192.168.0.4:9332 give You the same result then I would try another browser, if still the same I would try another version of python and rechecked whole installation process
Duce
Full Member
***
Offline Offline

Activity: 155


View Profile
January 07, 2015, 02:53:47 PM
 #11479

I have not seen this before and would like to know if anybody knows what this is. I did a search in this blog for any info but did not find any. I am running the Relay but did not see any association.  Undecided
Code:
2015-01-07 06:43:15.305684 Sending 415 shares to 198.167.143.123:49545
windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
January 07, 2015, 03:19:42 PM
 #11480

I have not seen this before and would like to know if anybody knows what this is. I did a search in this blog for any info but did not find any. I am running the Relay but did not see any association.  Undecided
Code:
2015-01-07 06:43:15.305684 Sending 415 shares to 198.167.143.123:49545

It's a recently launched node updating its p2pool share chain.

Pages: « 1 ... 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 613 614 615 616 617 618 619 620 621 622 623 624 ... 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!