As p3yot33at3r mentioned, Bitmain's awful fork of cgminer causes loss of hash rate on p2pool. Neither -ck nor kano have provided any official S7 cgminer patches, so you're stuck with using Bitmain's.
While changing the queue value can help, you're still going to lose hash rate if you mine on p2pool with virtually any Bitmain product.
Topic: S7 Hashrate on p2pool vs Centralized pools (Read 1376 times)
How to "search on a thread?" I am about to fire up my first s7. I read about a patch for cgminer somewhere, but I think it was last year and may not apply.
Thank you very much for your help,
Patricia
Thank you very much for your help,
Patricia
Hello Frank,
This has been discussed at length on the p2pool thread here: https://bitcointalksearch.org/topic/1500-th-p2pool-decentralized-dos-resistant-hop-proof-pool-18313 Search for S7 on that thread for an explanation.
Basically, Bitmain "broke" cgminer with their fork & seem unable/unwilling to fix it. Reducing the queue setting to 1 will help, but a slightly reduced hash rate is quite normal on p2pool.
Regards
This has been discussed at length on the p2pool thread here: https://bitcointalksearch.org/topic/1500-th-p2pool-decentralized-dos-resistant-hop-proof-pool-18313 Search for S7 on that thread for an explanation.
Basically, Bitmain "broke" cgminer with their fork & seem unable/unwilling to fix it. Reducing the queue setting to 1 will help, but a slightly reduced hash rate is quite normal on p2pool.
Regards
THNX! ;-)
Hello Frank,
This has been discussed at length on the p2pool thread here: https://bitcointalksearch.org/topic/1500-th-p2pool-decentralized-dos-resistant-hop-proof-pool-18313 Search for S7 on that thread for an explanation.
Basically, Bitmain "broke" cgminer with their fork & seem unable/unwilling to fix it. Reducing the queue setting to 1 will help, but a slightly reduced hash rate is quite normal on p2pool.
Regards
This has been discussed at length on the p2pool thread here: https://bitcointalksearch.org/topic/1500-th-p2pool-decentralized-dos-resistant-hop-proof-pool-18313 Search for S7 on that thread for an explanation.
Basically, Bitmain "broke" cgminer with their fork & seem unable/unwilling to fix it. Reducing the queue setting to 1 will help, but a slightly reduced hash rate is quite normal on p2pool.
Regards
HI All, pointing my S7 to the p2pool the reported hashrate drops around 20-% compared to Slush/Antpool,
Running a local node on 127.0.0.1 mac-min server quad-core 2Ghz i7 Ubuntu 4 gigs ram NO SSD.
---------------
p2pool.py output:
( Shares: 36 (3 orphan, 0 dead) Stale rate: ~8.3% (2-22%) Efficiency: ~108.5% (92-115%) at the time of writing.
--------------
Can someone explain the lower HR in comparison to centralized pools?
THANKS!
Running a local node on 127.0.0.1 mac-min server quad-core 2Ghz i7 Ubuntu 4 gigs ram NO SSD.
---------------
p2pool.py output:
( Shares: 36 (3 orphan, 0 dead) Stale rate: ~8.3% (2-22%) Efficiency: ~108.5% (92-115%) at the time of writing.
--------------
Can someone explain the lower HR in comparison to centralized pools?
THANKS!
Jump to: