Jump to content

Work Restarts?

Started By patws , Feb 28 2014 11:15 AM
miner restarts

Best Answer Cartman , 01 March 2014 - 08:39 PM

Yes, this is very much normal with p2pool.

 

P2Pool has it's own sharechain with a fast target speed of 10 seconds for most coins. This sharechain is used between nodes to distribute the work. Do not confuse the P2Pool sharechain with the coin blockchain. Since the P2Pool sharechain has such a rapid expiration of work you will notice a lot of restart messages to the miner.
 

I thought it was odd too until I looked further into how it works. It is a very common question/concern.

Go to the full post


  • Please log in to reply
2 replies to this topic

#1

patws
  • patws
  • New Member
  • MEMBER
  • Pip
  • 2 posts
  • 1 topics
    • Time Online: 12m 20s

What would cause repeated work restarts?  Using cgminer on BAMT with an XFX 270x and I'm not that familiar with p2pool mining :)  My reject rate is 5.2% and zero HW errors.

 

this is a sample of what I'm seeing:

 

[16:12:09] Stratum from Pool 0 requested work restart
[16:12:12] Pool 0 difficulty changed to 90.661840
[16:12:12] Stratum from Pool 0 requested work restart
[16:12:12] Stratum from Pool 0 requested work restart
[16:12:19] Accepted 01035c61 Diff 253/91 GPU 0 at Pool 0
[16:12:19] Accepted cea8c1c2 Diff 317/91 GPU 0 at Pool 0
[16:12:20] Pool 0 difficulty changed to 105.194150
[16:12:20] Network diff set to 1.72M
[16:12:20] Stratum from Pool 0 detected new block
[16:12:23] Accepted 0100b47e Diff 255/105 GPU 0 at Pool 0
[16:12:27] Pool 0 difficulty changed to 104.165357
[16:12:27] Stratum from Pool 0 requested work restart
[16:12:28] Pool 0 difficulty changed to 95.074645
[16:12:28] Stratum from Pool 0 requested work restart
[16:12:28] Pool 0 difficulty changed to 98.781009
[16:12:28] Network diff set to 1.72M
[16:12:28] Stratum from Pool 0 detected new block
 
Is this normal or have I configured something incorrectly?  I don't get this when using a regular pool.
 
cgminer.conf:
 
"intensity" : "18",
"worksize" : "512",
"kernel" : "ckolivas",
"lookup-gap" : "2",
"thread-concurrency" : "15323",
"gpu-threads" : "1",
"gpu-engine" : "1115",
"gpu-fan" : "0-100",
"gpu-memclock" : "1500",
"gpu-memdiff" : "0",
"gpu-powertune" : "20",
"gpu-vddc" : "1.115",
"temp-cutoff" : "95",
"temp-overheat" : "85",
"temp-target" : "75",
"api-listen" : true,
"api-mcast-port" : "4028",
"api-port" : "4028",
"auto-fan" : true,
"expiry" : "10",
"failover-switch-delay" : "30",
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"log" : "5",
"no-pool-disable" : true,
"queue" : "0",
"scan-time" : "5",
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin",
"api-allow" : "W:127.0.0.1"
 
 
Any help would be appreciated!
 
 

  • 0

Cryptocointalk.com doesn't endorse any ads. Warning: ads my be illegal or untrustworthy in your jurisdiction. Advertising Here.

#2

Cartman
  • Cartman
  • xPool.net Owner
  • POOL DEVELOPER
  • PipPip
  • 41 posts
  • 5 topics
    • Time Online: 10h 22m 56s

  Best Answer

Yes, this is very much normal with p2pool.

 

P2Pool has it's own sharechain with a fast target speed of 10 seconds for most coins. This sharechain is used between nodes to distribute the work. Do not confuse the P2Pool sharechain with the coin blockchain. Since the P2Pool sharechain has such a rapid expiration of work you will notice a lot of restart messages to the miner.
 

I thought it was odd too until I looked further into how it works. It is a very common question/concern.


  • 1

#3

patws
  • patws
  • New Member
  • MEMBER
  • Pip
  • 2 posts
  • 1 topics
    • Time Online: 12m 20s

Thank you for the answer - I wasn't sure if this was normal activity or not :)

 

I appreciate the help!


  • 0





Also tagged with one or more of these keywords: miner, restarts

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users