Bitcoin Forum
December 03, 2016, 06:48:41 AM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 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 613 614 615 616 617 618 619 620 621 622 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2028808 times)
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
January 02, 2015, 08:07:01 PM
 #11421

The arguments are share difficulty and pseudo share difficulty:

<bitcoin_address>/<share>+<pseudo_share>

Setting <share> to 0 defaults to lowest p2pool diff, setting <share> to any number less then current p2pool diff will result the minimum current diff

All setting pseudo share does is smooth out your graphs a little, it does not improve mining.

<pseudo_share> is recommended to be calculated as your hash rate in KH/s times 0.00000116

i.e. for an S3 that actually runs at 440GH/s: 440,000,000 * 0.00000116 = 510.4

M, to answer your question directly, here is the code from work.py, starting at line 299:

So you should be able to set it as high as you want...

I never understood the point of the /parm.  Just the +parm.

I tried setting my miners to +7000000 and they all come up as 999,999.

I got the same result with +5000000.

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.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
PatMan
Hero Member
*****
Offline Offline

Activity: 924


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


View Profile WWW
January 02, 2015, 08:15:00 PM
 #11422

Following up from my earlier post about my half dead S5, I had a pleasant surprise when UPS came knocking on my door with a replacement hashing board today - I didn't even realise that BitmainWarranty had despatched it! Straight away I got to work, stripped the S5, removed the offending board, slid in the new one & put it back together - it didn't take long at all due to the "open air" design...... Cheesy The result:



Running for 3 hours now without a hitch - lovely!  Smiley

Respect & thanks are due to BitmainWarranty who was super fast in arranging the replacement board without a hassle, as well as friendly & understanding as usual, unlike a certain other "representative" - who should take a leaf out of BitmainWarranty's book on customer relations instead of barking at customers. If he did so, Bitmain & himself would be far better for it.

Faith restored  Wink

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

Activity: 938


View Profile WWW
January 02, 2015, 08:50:28 PM
 #11423

The arguments are share difficulty and pseudo share difficulty:

<bitcoin_address>/<share>+<pseudo_share>

Setting <share> to 0 defaults to lowest p2pool diff, setting <share> to any number less then current p2pool diff will result the minimum current diff

All setting pseudo share does is smooth out your graphs a little, it does not improve mining.

<pseudo_share> is recommended to be calculated as your hash rate in KH/s times 0.00000116

i.e. for an S3 that actually runs at 440GH/s: 440,000,000 * 0.00000116 = 510.4

M, to answer your question directly, here is the code from work.py, starting at line 299:

So you should be able to set it as high as you want...

I never understood the point of the /parm.  Just the +parm.

I tried setting my miners to +7000000 and they all come up as 999,999.

I got the same result with +5000000.

M

I wonder if the limitation is in CGMiner?

mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
January 02, 2015, 09:12:09 PM
 #11424

The arguments are share difficulty and pseudo share difficulty:

<bitcoin_address>/<share>+<pseudo_share>

Setting <share> to 0 defaults to lowest p2pool diff, setting <share> to any number less then current p2pool diff will result the minimum current diff

All setting pseudo share does is smooth out your graphs a little, it does not improve mining.

<pseudo_share> is recommended to be calculated as your hash rate in KH/s times 0.00000116

i.e. for an S3 that actually runs at 440GH/s: 440,000,000 * 0.00000116 = 510.4

M, to answer your question directly, here is the code from work.py, starting at line 299:

So you should be able to set it as high as you want...

I never understood the point of the /parm.  Just the +parm.

I tried setting my miners to +7000000 and they all come up as 999,999.

I got the same result with +5000000.

M

I wonder if the limitation is in CGMiner?

on the p2pool node I see work size of 999,999.

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
Hero Member
*****
Offline Offline

Activity: 994


Mine at Jonny's Pool


View Profile WWW
January 02, 2015, 09:57:50 PM
 #11425

The arguments are share difficulty and pseudo share difficulty:

<bitcoin_address>/<share>+<pseudo_share>

Setting <share> to 0 defaults to lowest p2pool diff, setting <share> to any number less then current p2pool diff will result the minimum current diff

All setting pseudo share does is smooth out your graphs a little, it does not improve mining.

<pseudo_share> is recommended to be calculated as your hash rate in KH/s times 0.00000116

i.e. for an S3 that actually runs at 440GH/s: 440,000,000 * 0.00000116 = 510.4

M, to answer your question directly, here is the code from work.py, starting at line 299:

So you should be able to set it as high as you want...

I never understood the point of the /parm.  Just the +parm.

I tried setting my miners to +7000000 and they all come up as 999,999.

I got the same result with +5000000.

M

I wonder if the limitation is in CGMiner?

on the p2pool node I see work size of 999,999.

M
It's limited in p2pool.  You guys are looking in the wrong spot.  From bitcoin/networks.py:
Code:
SANE_TARGET_RANGE = (2**256//2**32//1000000 - 1, 2**256//2**32 - 1)

Here's the implementation of its usage in work.py:
Code:
if desired_pseudoshare_target is None:
    target = 2**256-1
    local_hash_rate = self._estimate_local_hash_rate()
    if local_hash_rate is not None:
        target = min(target,
            bitcoin_data.average_attempts_to_target(local_hash_rate * 1)) # limit to 1 share response every second by modulating pseudoshare difficulty
else:
    target = desired_pseudoshare_target
target = max(target, share_info['bits'].target)
for aux_work, index, hashes in mm_later:
    target = max(target, aux_work['target'])
target = math.clip(target, self.node.net.PARENT.SANE_TARGET_RANGE)

The difference between '+' and '/' is that '+' sets the pseudo-share difficulty (i.e. shares that p2pool cares about recording from this particular BTC address) and '/' can have an effect on your payouts if you set it higher than p2pool's minimum share difficulty.

Set '+' too low and you'll see really pretty graphs with far fewer spikes because the node starts to care about more and more meaningless shares.  You're also likely to see a whole lot more of those "Miner submitted share more than once" messages in your logs.

Set '/' lower than current p2pool share difficulty and its meaningless.  Set it above current p2pool share difficulty and even if your miner finds a share that would satisfy the requirements and end up on the chain, it will not be counted unless it also meets the difficulty requirements you set by using the '/' parameter.  The benefit of this is that each share you DO submit is more heavily weighted than the "normal" shares, so it's worth more.  At this point in the game, unless you're bringing a few hundred TH/s onto a node, there's no need to use this parameter at all.

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

Activity: 1358


View Profile
January 02, 2015, 10:34:14 PM
 #11426

It's limited in p2pool.  You guys are looking in the wrong spot.  From bitcoin/networks.py:
Code:
SANE_TARGET_RANGE = (2**256//2**32//1000000 - 1, 2**256//2**32 - 1)

Here's the implementation of its usage in work.py:
Code:
if desired_pseudoshare_target is None:
    target = 2**256-1
    local_hash_rate = self._estimate_local_hash_rate()
    if local_hash_rate is not None:
        target = min(target,
            bitcoin_data.average_attempts_to_target(local_hash_rate * 1)) # limit to 1 share response every second by modulating pseudoshare difficulty
else:
    target = desired_pseudoshare_target
target = max(target, share_info['bits'].target)
for aux_work, index, hashes in mm_later:
    target = max(target, aux_work['target'])
target = math.clip(target, self.node.net.PARENT.SANE_TARGET_RANGE)

The difference between '+' and '/' is that '+' sets the pseudo-share difficulty (i.e. shares that p2pool cares about recording from this particular BTC address) and '/' can have an effect on your payouts if you set it higher than p2pool's minimum share difficulty.

Set '+' too low and you'll see really pretty graphs with far fewer spikes because the node starts to care about more and more meaningless shares.  You're also likely to see a whole lot more of those "Miner submitted share more than once" messages in your logs.

Set '/' lower than current p2pool share difficulty and its meaningless.  Set it above current p2pool share difficulty and even if your miner finds a share that would satisfy the requirements and end up on the chain, it will not be counted unless it also meets the difficulty requirements you set by using the '/' parameter.  The benefit of this is that each share you DO submit is more heavily weighted than the "normal" shares, so it's worth more.  At this point in the game, unless you're bringing a few hundred TH/s onto a node, there's no need to use this parameter at all.

I was trying to set the pseudo share size high to reduce my bandwidth usage.  I'm still constricted by my DSL bandwidth. Sad

Thanks for proving what I saw. 

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
Hero Member
*****
Offline Offline

Activity: 994


Mine at Jonny's Pool


View Profile WWW
January 02, 2015, 10:44:27 PM
 #11427



I was trying to set the pseudo share size high to reduce my bandwidth usage.  I'm still constricted by my DSL bandwidth. Sad

Thanks for proving what I saw.  

M
Your miners and your node aren't on the same network I presume?  Can you run your p2pool node on the same local network as your miners?  The vast majority of the bandwidth being consumed by p2pool is the broadcasting of the share chain data, not the data from your miners.  I don't know how you've got things setup (like co-located miners, but running the p2pool node from your home PC, or miners in your home, but running the p2pool node on a VPS).

Bandwidth limitations suck.  Sorry you're suffering from it Sad

EDIT: one thing you can do, if you haven't, is to ensure you aren't accepting traffic on 9333.  Yeah, it'll turn off incoming connections to your node, but it'll definitely reduce your overall usage.  You can also limit your connections to bitcoind and/or not allow traffic on port 8333.

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

Activity: 1358


View Profile
January 02, 2015, 11:35:00 PM
 #11428



I was trying to set the pseudo share size high to reduce my bandwidth usage.  I'm still constricted by my DSL bandwidth. Sad

Thanks for proving what I saw.  

M
Your miners and your node aren't on the same network I presume?  Can you run your p2pool node on the same local network as your miners?  The vast majority of the bandwidth being consumed by p2pool is the broadcasting of the share chain data, not the data from your miners.  I don't know how you've got things setup (like co-located miners, but running the p2pool node from your home PC, or miners in your home, but running the p2pool node on a VPS).

Bandwidth limitations suck.  Sorry you're suffering from it Sad

EDIT: one thing you can do, if you haven't, is to ensure you aren't accepting traffic on 9333.  Yeah, it'll turn off incoming connections to your node, but it'll definitely reduce your overall usage.  You can also limit your connections to bitcoind and/or not allow traffic on port 8333.

Nothing is coming in, and outgoing connections are limited.

I have a VPS node, but it's on the other side of the country.  I get 16% stale if I use it compared to 1.5% local. Sad

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
Hero Member
*****
Offline Offline

Activity: 994


Mine at Jonny's Pool


View Profile WWW
January 02, 2015, 11:41:55 PM
 #11429



I was trying to set the pseudo share size high to reduce my bandwidth usage.  I'm still constricted by my DSL bandwidth. Sad

Thanks for proving what I saw.  

M
Your miners and your node aren't on the same network I presume?  Can you run your p2pool node on the same local network as your miners?  The vast majority of the bandwidth being consumed by p2pool is the broadcasting of the share chain data, not the data from your miners.  I don't know how you've got things setup (like co-located miners, but running the p2pool node from your home PC, or miners in your home, but running the p2pool node on a VPS).

Bandwidth limitations suck.  Sorry you're suffering from it Sad

EDIT: one thing you can do, if you haven't, is to ensure you aren't accepting traffic on 9333.  Yeah, it'll turn off incoming connections to your node, but it'll definitely reduce your overall usage.  You can also limit your connections to bitcoind and/or not allow traffic on port 8333.

Nothing is coming in, and outgoing connections are limited.

I have a VPS node, but it's on the other side of the country.  I get 16% stale if I use it compared to 1.5% local. Sad

M
If your miners and node are local, then that traffic is not going outbound, so it wouldn't impact your bandwidth limitations.  I figured you'd already done the connection limit and shut down the inbound ports, but thought I'd mention it in case anyone else happened to have bandwidth limitations and hadn't done so yet.

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

Activity: 1358


View Profile
January 03, 2015, 12:00:18 AM
 #11430

If your miners and node are local, then that traffic is not going outbound, so it wouldn't impact your bandwidth limitations.  I figured you'd already done the connection limit and shut down the inbound ports, but thought I'd mention it in case anyone else happened to have bandwidth limitations and hadn't done so yet.

I've been trying different things.  The large share size when was I was trying to use my VPS.

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 03, 2015, 03:25:34 AM
 #11431


It's limited in p2pool.  You guys are looking in the wrong spot.  From bitcoin/networks.py:
Code:
SANE_TARGET_RANGE = (2**256//2**32//1000000 - 1, 2**256//2**32 - 1)


Aha! Thanks Smiley

IYFTech
Hero Member
*****
Offline Offline

Activity: 686


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


View Profile
January 03, 2015, 10:43:27 AM
 #11432

Following up from my earlier post about my half dead S5, I had a pleasant surprise when UPS came knocking on my door with a replacement hashing board today - I didn't even realise that BitmainWarranty had despatched it! Straight away I got to work, stripped the S5, removed the offending board, slid in the new one & put it back together - it didn't take long at all due to the "open air" design...... Cheesy The result:

Running for 3 hours now without a hitch - lovely!  Smiley

Respect & thanks are due to BitmainWarranty who was super fast in arranging the replacement board without a hassle, as well as friendly & understanding as usual, unlike a certain other "representative" - who should take a leaf out of BitmainWarranty's book on customer relations instead of barking at customers. If he did so, Bitmain & himself would be far better for it.

Faith restored  Wink

Nice one! So we needn't have spent hours with a hangover trying to fix it the day before then?  Cheesy Cheesy Cheesy

Thanks for the New Years Eve party dude, great fun!

I can highly recommend PatMans good lady's fried breakfast in the morning - absolute class!  Grin

-- 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
PatMan
Hero Member
*****
Offline Offline

Activity: 924


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


View Profile WWW
January 03, 2015, 01:00:39 PM
 #11433

I can highly recommend PatMans good lady's fried breakfast in the morning - absolute class!  Grin

Flattery will get you everywhere...... Wink

"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
January 03, 2015, 01:07:55 PM
 #11434

I can highly recommend PatMans good lady's fried breakfast in the morning - absolute class!  Grin

Flattery will get you everywhere...... Wink

Can You please share real consumption at the wall of this S5?
PatMan
Hero Member
*****
Offline Offline

Activity: 924


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


View Profile WWW
January 03, 2015, 01:14:01 PM
 #11435

I can highly recommend PatMans good lady's fried breakfast in the morning - absolute class!  Grin

Flattery will get you everywhere...... Wink

Can You please share real consumption at the wall of this S5?

I don't have the equipment to measure it I'm afraid - but you should find that on the Bitmain S5 thread  Wink

"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
January 03, 2015, 01:28:21 PM
 #11436

I can highly recommend PatMans good lady's fried breakfast in the morning - absolute class!  Grin

Flattery will get you everywhere...... Wink

Can You please share real consumption at the wall of this S5?

I don't have the equipment to measure it I'm afraid - but you should find that on the Bitmain S5 thread  Wink

Ok, I have found this:

"After running for an hour, it settled into:

Miner Speed: 1155 GH/s
BTCGuild Speed: 1145 GH/s
Power: 675 W (750 W Bronze PSU)"

this is what we probably can believe to (unfortunately guy is mining at wrong pool)
grn
Sr. Member
****
Offline Offline

Activity: 328


View Profile
January 04, 2015, 02:31:19 AM
 #11437

p2pool on windows 8 problem. when i try to see the stats page at 127.0.0.1:9332 I get this

Installed
Python 2.7
Twisted 14.0.2
zope.interface 4.1.2
pywin32-218.win32-py2.7.exe
WMI-1.4.9.win32.exe


web.Server Traceback (most recent call last):
exceptions.TypeError: Can only pass-through bytes on Python 2
C:\Python27\lib\site-packages\twisted\web\server.py:189 in process
188                    self._encoder = encoder
189            self.render(resrc)
190        except:
C:\Python27\lib\site-packages\twisted\web\server.py:238 in render
237        try:
238            body = resrc.render(self)
239        except UnsupportedMethod as e:
C:\Python27\lib\site-packages\twisted\web\resource.py:250 in render
249            raise UnsupportedMethod(allowedMethods)
250        return m(request)
251
C:\Python27\lib\site-packages\twisted\web\static.py:631 in render_GET
630
631        producer.start()
632        # and make sure the connection doesn't get closed
C:\Python27\lib\site-packages\twisted\web\static.py:710 in start
709    def start(self):
710        self.request.registerProducer(self, False)
711
C:\Python27\lib\site-packages\twisted\web\http.py:873 in registerProducer
872        else:
873            self.transport.registerProducer(producer, streaming)
874
C:\Python27\lib\site-packages\twisted\internet\abstract.py:112 in registerProducer
111            if not streaming:
112                producer.resumeProducing()
113
C:\Python27\lib\site-packages\twisted\web\static.py:720 in resumeProducing
719            # .resumeProducing again, so be prepared for a re-entrant call
720            self.request.write(data)
721        else:
C:\Python27\lib\site-packages\twisted\web\server.py:217 in write
216                data = self._encoder.encode(data)
217            http.Request.write(self, data)
218
C:\Python27\lib\site-packages\twisted\web\http.py:1002 in write
1001                        # Backward compatible cast for non-bytes values
1002                        value = networkString('%s' % (value,))
1003                    l.extend([name, b": ", value, b"\r\n"])
C:\Python27\lib\site-packages\twisted\python\compat.py:364 in networkString
363        if not isinstance(s, str):
364            raise TypeError("Can only pass-through bytes on Python 2")
365        # Ensure we're limited to ASCII subset:
exceptions.TypeError: Can only pass-through bytes on Python 2

Any Ideas?

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

Activity: 938


View Profile WWW
January 04, 2015, 05:43:24 AM
 #11438

p2pool on windows 8 problem. when i try to see the stats page at 127.0.0.1:9332 I get this
....
Any Ideas?

Not a Windows guy, but I would try updating/reinstalling Python...



windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
January 04, 2015, 05:44:28 AM
 #11439

6 blocks in 7 minutes, wow.... (bitcoin wide, not p2pool Wink)




grn
Sr. Member
****
Offline Offline

Activity: 328


View Profile
January 04, 2015, 06:30:33 AM
 #11440

p2pool on windows 8 problem. when i try to see the stats page at 127.0.0.1:9332 I get this
....
Any Ideas?

Not a Windows guy, but I would try updating/reinstalling Python...




not a windows guy either but all i have at home is a laptop>>>tried reinstall

How is that Lexical analysis working out bickneleski?
Pages: « 1 ... 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 613 614 615 616 617 618 619 620 621 622 ... 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!