Bitcoin Forum
December 06, 2016, 07:49:39 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 ... 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 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2031875 times)
TheAnalogKid
Sr. Member
****
Offline Offline

Activity: 266


View Profile
March 26, 2015, 06:02:15 PM
 #12361

To put it simply, the larger the hash rate of the pool, the more difficult it becomes to find a share and get it on the chain for payout.  It's precisely the opposite problem of your more traditional pool.  The higher the difficulty, the more variance experienced by the smaller miner, which discourages smaller miners from mining here.
What he said.

A few months back when the pool was around 2PH the share difficulty for P2Pool rose to the point where more often than not if you were mining with less than the equivalent of an S1 (200GH/s) you wouldn't lodge a share within 1 day, which would mean all your effort for the day would end up not counting and you were essentially mining for nothing, and you wouldn't receive any credit towards the block rewards.

In addition, a single large miner could in effect swamp out all smaller miners on the node, because the larger miners would raise the share difficulty which was appropriate for the larger miner, but not good for the smaller miners.  If the larger miner was not considerate or couldn't break up the hashrate into smaller chunks, it was bad for the rest of the miners on the node.

The higher the pool hashrate, the higher the share difficulty, the harder it is for small miners to solve shares and they lose out.  Eventually you're talking about even an S3 not making any shares on the chain in time, which at this point there's still a ton of them deployed.

The money raised from these ads will be used to pay for improved forum software and other useful stuff.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
Songminer
Member
**
Offline Offline

Activity: 67


View Profile
March 26, 2015, 06:37:28 PM
 #12362

To put it simply, the larger the hash rate of the pool, the more difficult it becomes to find a share and get it on the chain for payout.  It's precisely the opposite problem of your more traditional pool.  The higher the difficulty, the more variance experienced by the smaller miner, which discourages smaller miners from mining here.
What he said.

A few months back when the pool was around 2PH the share difficulty for P2Pool rose to the point where more often than not if you were mining with less than the equivalent of an S1 (200GH/s) you wouldn't lodge a share within 1 day, which would mean all your effort for the day would end up not counting and you were essentially mining for nothing, and you wouldn't receive any credit towards the block rewards.

In addition, a single large miner could in effect swamp out all smaller miners on the node, because the larger miners would raise the share difficulty which was appropriate for the larger miner, but not good for the smaller miners.  If the larger miner was not considerate or couldn't break up the hashrate into smaller chunks, it was bad for the rest of the miners on the node.

The higher the pool hashrate, the higher the share difficulty, the harder it is for small miners to solve shares and they lose out.  Eventually you're talking about even an S3 not making any shares on the chain in time, which at this point there's still a ton of them deployed.

Is it as simple as sub-dividing the shares and/or reducing the time between shares?  In concept, of course.
TheAnalogKid
Sr. Member
****
Offline Offline

Activity: 266


View Profile
March 26, 2015, 08:05:53 PM
 #12363

To put it simply, the larger the hash rate of the pool, the more difficult it becomes to find a share and get it on the chain for payout.  It's precisely the opposite problem of your more traditional pool.  The higher the difficulty, the more variance experienced by the smaller miner, which discourages smaller miners from mining here.
What he said.

A few months back when the pool was around 2PH the share difficulty for P2Pool rose to the point where more often than not if you were mining with less than the equivalent of an S1 (200GH/s) you wouldn't lodge a share within 1 day, which would mean all your effort for the day would end up not counting and you were essentially mining for nothing, and you wouldn't receive any credit towards the block rewards.

In addition, a single large miner could in effect swamp out all smaller miners on the node, because the larger miners would raise the share difficulty which was appropriate for the larger miner, but not good for the smaller miners.  If the larger miner was not considerate or couldn't break up the hashrate into smaller chunks, it was bad for the rest of the miners on the node.

The higher the pool hashrate, the higher the share difficulty, the harder it is for small miners to solve shares and they lose out.  Eventually you're talking about even an S3 not making any shares on the chain in time, which at this point there's still a ton of them deployed.

Is it as simple as sub-dividing the shares and/or reducing the time between shares?  In concept, of course.

Unfortunately I don't believe it's that simple.  I'm no developer, but from my understanding it's quite an involved issue within the code and not easily fixed.  Hence the reason it's sat for so long like this... I'm sure there's capable devs who would have done it if it were not too involved already.

MissouriMiner
Full Member
***
Offline Offline

Activity: 164



View Profile WWW
March 28, 2015, 07:53:51 PM
 #12364

Info and question regarding "Share above target" messages when mining with Antminer S5's.  I also post this info in the AntMiner S5 forum.  

My S5's get a lot of "Share above target" messages.  I'm mining with my own local Bitcoin P2Pool node.  The node performance is fine, GWT Latency is fine (<300ms daily average).  The share above target messages are only seen when I enable Verbose mode with cgminer.  Hashrate and Work Utility stats seem fine.  My question is, is this a problem?  Thanks.

EDIT1:  So far, I only see these messages with P2Pool.  Manually setting pseudo share difficulty reduced the messages, as long as I didn't set the value too high, which I don't understand.  I'm using BTCADDRESS+1024   Again, the share above target messages can only be seen if verbose mode is enabled.  I don't know if this is a real issue or not.  I tried other P2Pool nodes too, with the same result.

EDIT2:  Some more detail.  I get the same "Share above target" messages with both default Bitmain version of cgminer 4.8.0 and ckolivas version 4.9.0-150105.  On the server side, I'm using Forrest's latest p2pool version 13.4-67-gbcd9a50, and bitcoind v10.  

Example below from cgminer screen.  These messages are from when I do not use +1024 to set pseudo share difficulty.

 [2015-03-28 20:14:26] Accepted 420e19cc Diff 992/693 BTM 0 pool 0
 [2015-03-28 20:14:29] BTM 0: Share above target
 [2015-03-28 20:14:26] Submitting share 00420e19 to pool 0
 [2015-03-28 20:14:26] Accepted 420e19cc Diff 992/693 BTM 0 pool 0
 [2015-03-28 20:14:29] BTM 0: Share above target
 [2015-03-28 20:14:31] BitMain RxStatus Token: v(0) chip_status_eft(0) detect_get(0) chip_address(00) reg_address(00) crc(ef82)
 [2015-03-28 20:14:31] BitMain RxStatus tmp :0x01  byte4 0x00 chip_value_eft 0 reserved 0 get_blk_num 0
 [2015-03-28 20:14:31] bitmain_parse_results v=0 chain=2 fifo=1119 hwv1=3 hwv2=4 hwv3=3 hwv4=0 nerr=1-1 freq=350 chain info:
 [2015-03-28 20:14:31] bitmain_parse_results chain(0) asic_num=30 asic_status=oooooooo oooooooo oooooooo oooooo
 [2015-03-28 20:14:31] bitmain_parse_results chain(1) asic_num=30 asic_status=oooooooo oooooooo oooooooo oooooo
 [2015-03-28 20:14:31] BitMain: Fan1: 3600/m, Fan2: 0/m, Fan3: 0/m, Fan4: 0/m   Temp1: 46C, Temp2: 52C, TempMAX: 52C
 [2015-03-28 20:14:31] (5s):1.350T (1m):726.8G (5m):634.6G (15m):376.5G (avg):1.126Th/s
 [2015-03-28 20:14:32] Submitting share 004bfbe4 to pool 0
 [2015-03-28 20:14:32] Accepted 4bfbe476 Diff 862/693 BTM 0 pool 0
 [2015-03-28 20:14:37] (5s):1.348T (1m):752.3G (5m):641.3G (15m):379.9G (avg):1.128Th/s
 [2015-03-28 20:14:37] Submitting share 002bbf14 to pool 0
 [2015-03-28 20:14:37] Accepted 2bbf14b4 Diff 1.5K/693 BTM 0 pool 0
 [2015-03-28 20:14:37] Submitting share 0022698b to pool 0
 [2015-03-28 20:14:37] Accepted 22698bb1 Diff 1.9K/693 BTM 0 pool 0
 [2015-03-28 20:14:38] BTM 0: Share above target
 [2015-03-28 20:14:38] Submitting share 005b0202 to pool 0
 [2015-03-28 20:14:38] Accepted 5b0202ef Diff 720/693 BTM 0 pool 0
 [2015-03-28 20:14:39] BTM 0: Share above target
 [2015-03-28 20:14:41] BTM 0: Share above target
 [2015-03-28 20:14:42] Submitting share 004065d4 to pool 0
 [2015-03-28 20:14:42] Accepted 4065d40a Diff 1.02K/693 BTM 0 pool 0
 [2015-03-28 20:14:42] (5s):1.380T (1m):760.7G (5m):643.3G (15m):380.8G (avg):1.129Th/s
 [2015-03-28 20:14:44] Submitting share 000f245c to pool 0
 [2015-03-28 20:14:44] Accepted 0f245c1b Diff 4.33K/693 BTM 0 pool 0
 [2015-03-28 20:14:44] Submitting share 001b406e to pool 0
 [2015-03-28 20:14:44] Accepted 1b406edc Diff 2.4K/693 BTM 0 pool 0
 [2015-03-28 20:14:45] BTM 0: Share above target
 [2015-03-28 20:14:45] Submitting share 00172458 to pool 0
 [2015-03-28 20:14:45] Accepted 1724589d Diff 2.83K/693 BTM 0 pool 0
 [2015-03-28 20:14:46] Submitting share 001d53b0 to pool 0
 [2015-03-28 20:14:46] Accepted 1d53b0d9 Diff 2.23K/693 BTM 0 pool 0
 [2015-03-28 20:14:46] Submitting share 000c9a25 to pool 0
 [2015-03-28 20:14:46] Accepted 0c9a2573 Diff 5.2K/693 BTM 0 pool 0
 [2015-03-28 20:14:47] BitMain RxStatus Token: v(0) chip_status_eft(0) detect_get(0) chip_address(00) reg_address(00) crc(ef82)
 [2015-03-28 20:14:47] BitMain RxStatus tmp :0x01  byte4 0x00 chip_value_eft 0 reserved 0 get_blk_num 0
 [2015-03-28 20:14:47] bitmain_parse_results v=0 chain=2 fifo=364 hwv1=3 hwv2=4 hwv3=3 hwv4=0 nerr=1-1 freq=350 chain info:
 [2015-03-28 20:14:47] bitmain_parse_results chain(0) asic_num=30 asic_status=oooooooo oooooooo oooooooo oooooo
 [2015-03-28 20:14:47] bitmain_parse_results chain(1) asic_num=30 asic_status=oooooooo oooooooo oooooooo oooooo
 [2015-03-28 20:14:47] BitMain: Fan1: 3600/m, Fan2: 0/m, Fan3: 0/m, Fan4: 0/m   Temp1: 46C, Temp2: 52C, TempMAX: 52C
 [2015-03-28 20:14:47] BTM 0: Share above target
 [2015-03-28 20:14:47] (5s):1.393T (1m):783.5G (5m):648.2G (15m):382.7G (avg):1.130Th/s
 [2015-03-28 20:14:47] Pool 0 difficulty changed to 692.5
 [2015-03-28 20:14:47] Stratum from pool 0 requested work restart
 [2015-03-28 20:14:47] Work update message received
 [2015-03-28 20:14:47] bitmain_flush_work queued=0 array=4696
kano
Legendary
*
Offline Offline

Activity: 1918


Linux since 1997 RedHat 4


View Profile
March 28, 2015, 11:22:13 PM
 #12365

... don't forget that the share messages don't actually mean anything (unless they are share-chain shares)
They are just an attempt to divine your hash rate.

Pool: https://kano.is BTC: 1KanoiBupPiZfkwqB7rfLXAzPnoTshAVmb
CKPool and CGMiner developer, IRC FreeNode #ckpool and #cgminer kanoi
Help keep Bitcoin secure by mining on pools with Stratum, the best protocol to mine Bitcoins with ASIC hardware
MissouriMiner
Full Member
***
Offline Offline

Activity: 164



View Profile WWW
March 28, 2015, 11:30:37 PM
 #12366

... don't forget that the share messages don't actually mean anything (unless they are share-chain shares)
They are just an attempt to divine your hash rate.

Oh good.  Thanks.
Songminer
Member
**
Offline Offline

Activity: 67


View Profile
March 30, 2015, 01:25:00 PM
 #12367

Block.  Long time coming.
jonnybravo0311
Legendary
*
Online Online

Activity: 1008


Mine at Jonny's Pool


View Profile WWW
March 30, 2015, 03:58:32 PM
 #12368

Block.  Long time coming.
While it is always unpleasant to see a multi-day stretch of no block solves, the reality is that this wasn't so bad in the grand scheme of things.  With the current difficulty level, and assuming p2pool averages 1.5PH/s, we can expect a block every 37 hours or so.  This last one was about 78 hours - just over 200%... a CDF of about 0.89 or so.

Now we just need a few quick blocks Smiley

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

Activity: 1078



View Profile
March 30, 2015, 05:02:14 PM
 #12369

the reality is that this wasn't so bad in the grand scheme of things.

True.

Patience pay ... on P2Pool even with ultra-low power.

French ... but not so much   ---===---   P2P ... it's people at the end   ---===---   P2Pool (10,9 GH/s).
Comment miner des bitcoins ? Un tutoriel est là : https://bitcointalk.org/index.php?topic=1114415.0
Bitcoin change everything ... an explain of this fact : https://www.youtube.com/watch?v=joITmEr4SjY
jonnybravo0311
Legendary
*
Online Online

Activity: 1008


Mine at Jonny's Pool


View Profile WWW
March 31, 2015, 01:39:22 AM
 #12370

Well would you look at that... 3 blocks so far today...

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

Activity: 1050



View Profile
March 31, 2015, 01:42:11 AM
 #12371

Well would you look at that... 3 blocks so far today...

I pointed some rental toward CK solo but had almost pointed here instead.... I chose poorly...
iegservers
Member
**
Offline Offline

Activity: 62


View Profile WWW
March 31, 2015, 01:42:46 AM
 #12372

Well would you look at that... 3 blocks so far today...
Its Digital Joy https://www.youtube.com/watch?v=zS1cLOIxsQ8

http://iEGServers.com - "If you have found my posts to be informative, please dontate btc to : 1DSMgKPbQSRCmmBptebKYnNugxSmWHMzca
jonnybravo0311
Legendary
*
Online Online

Activity: 1008


Mine at Jonny's Pool


View Profile WWW
March 31, 2015, 01:44:40 AM
 #12373

Well would you look at that... 3 blocks so far today...

I pointed some rental toward CK solo but had almost pointed here instead.... I chose poorly...
Well my gear has spent most of its time being rented or pointed to ck's solo pool the past few days so these three blocks equaled about what I would expect in a single block payment... Definitely not complaining though...

Edit: the latest block found on ck's solo pool was found by a guy with half an S5... 550GH/s.

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.
TheAnalogKid
Sr. Member
****
Offline Offline

Activity: 266


View Profile
March 31, 2015, 02:22:51 AM
 #12374

Well would you look at that... 3 blocks so far today...

I pointed some rental toward CK solo but had almost pointed here instead.... I chose poorly...
Well my gear has spent most of its time being rented or pointed to ck's solo pool the past few days so these three blocks equaled about what I would expect in a single block payment... Definitely not complaining though...

Edit: the latest block found on ck's solo pool was found by a guy with half an S5... 550GH/s.
Same here, most of my miners have been rented solid for most of the past week, so I didn't get too many shares on this round.  However, the miner I've been running on nasty pool for donations has been there solid, so at least that's cashing in... Should be a good week for seat donations Smiley

As for solo, I had almost 90th pointed there over most of the weekend and got bubkis.  This guy had 550gh and landed a block (over two months, yeah, but still).  Go figure  Shocked

windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
March 31, 2015, 02:49:33 AM
 #12375

Well would you look at that... 3 blocks so far today...


IYFTech
Hero Member
*****
Offline Offline

Activity: 686


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


View Profile
March 31, 2015, 02:50:00 AM
 #12376

I pointed a few S3's back here when the hash rate dropped back down below 2PH, I hardly lost any shares & the blocks started rolling in again - nice  Grin  2PH & below seems to be the sweet spot atm, any higher & it grinds to a halt....... Tongue

-- 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
lightfoot
Legendary
*
Offline Offline

Activity: 980

Hacking KNC stuff because it goes FOOM well.


View Profile
March 31, 2015, 02:51:17 AM
 #12377

Lady luck has come to the P2p00l today...



Remember, she is fickle....
nreal
Full Member
***
Offline Offline

Activity: 182


View Profile
March 31, 2015, 06:45:37 AM
 #12378

Stay away from Bitmain!

The official announcement from thei www...

"UMISOO Minerals mine equipment maintenance outage will be a temporary power outage, I'm sorry, this will give you an early loss, we will give you compensation at the end or the next."

2 Emails from webmaster

Hello, I'm really sorry! Summer to come, need to re-deploy mines to facilitate mining machine of heat, which can increase the life of the mining machine operators and improve strength. We also carry out mining machine maintenance cleaning. In the end, we will give you appropriate compensation, I hope you can understand.


Best wishes! Umisoo 21.3.2015


Dear User,

We are so sorry to inform that your miners have been turned off due to the relocation of Umisoo's mining farm. The new relocated mining farm is owned by Bitmain, while it is no longer suitable for the continuation of the previous Umisoo type's hosting service, because new mining farm is located in a remote rural area installing with small limited bandwidth, and exporting IP for strict secrecy.


 In order fix the trouble that caused:

1> Umisoo will buy the S4 market from Hashnest.com to compensate the hosted hardware, e.g.: User who owns one hosted S4 will get        2Th/s of S4 market on Hashnest platform.
2> Hosting service fee on Umisoo is 0.11 US$/kWh, while the maintenance fee on Hashnest is 0.0967 US$/kWh.
3> Umisoo will compensate the downtime loss based on 100% PPS payout. Compensation will be issued to your account on Hashnest.
4> Your balance of hosting service fee on Umisoo will be transacted to your account on Hashnest.
5> Please submit your account on Hashnest to Umisoo (webmaster@umisoo.com) to speed the transfer.

Our truly apologies again, Looking forward to receive your reply and move on.

Umisoo

March 30, 2015

Im not a bitmain customer anymore !!


Here in Finland this would be called crime.
jedimstr
Hero Member
*****
Offline Offline

Activity: 784



View Profile
March 31, 2015, 10:26:09 AM
 #12379

Stay away from Bitmain!


... snip long rant...


Im not a bitmain customer anymore !!

Here in Finland this would be called crime.


So what does this have to do with p2pool? You sure you've got the right thread for this?

nreal
Full Member
***
Offline Offline

Activity: 182


View Profile
March 31, 2015, 11:00:21 AM
 #12380

Stay away from Bitmain!


... snip long rant...


Im not a bitmain customer anymore !!

Here in Finland this would be called crime.


So what does this have to do with p2pool? You sure you've got the right thread for this?

Yes I´m sure. Bitmain folks tell lies to users who wish to use p2pool, they told that it would be possible to change miners settings at umisoo when miners are there. When it arrived they told me that their engineers think that im wrong and i should be happy with alot dead... 30-50% at the time. And now this - lying and....

How much do you think p2pool looses because ants wont submit doa shares?  Or do You think that everyone replaces that not working cgminer with working one? Bitmain works against p2pool.

Pages: « 1 ... 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 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 ... 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!