Topic: BOUNTY: 0.5BTC = 7970, cgminer, p2pool, reject rate > 12% :( (Read 6209 times)

For p2pool everyone here is exactly right, you need to drop to 1 thread, maybe 2 at most.
Do you get something similar on other pools?

try 128 or 256 worksize... diakgcn kernel instead of poclbm



I have never used p2pool...... but 12% seems insanely high

How many rigs?

I have three rigs with 7970s.  One has 4, one has 3, and my workstation has 1.  I average between 2-7% reject rate.

I agree with the others, 5 threads is too high.  But I've been using 2 threads without a problem for a long time.  I just changed mine to 1 to see what changes.

From my experience high rejects can come from a few things:

1 - make sure you have your p2pool port forwarded by your router to your p2pool
2 - don't run p2pool on a machine that is limited in memory or CPU.  at least dual core, and you want to have enough memory for the OS and apps so that you aren't swapping.  since memory is dirt cheap, I have 4 gigs on all my miners.  my main p2pool server has 3 cores.
3 - keep your network latency as minimal as possible.  for example, run p2pool and bitcoind on the same box.

here I have p2pool on two boxes, with my main one being the one with 4 gpus.  I run p2pool on non standard ports and have my router configured to forward the ports to each, so I have a high number of incoming and outgoing connections on each.  I also forcibly connect them to each other with -n. 

Here's my cgminer.conf from my main miner:

"intensity" : "9,9,9,9",
"vectors" : "1,1,1,1",
"worksize" : "64,64,64,64",
"kernel" : "poclbm,poclbm,poclbm,poclbm",
"gpu-engine" : "0-1125,0-1125,0-1125,0-1125",
"gpu-fan" : "60,60,60,60",
"temp-cutoff" : "90,90,90,90",
"temp-overheat" : "85,85,85,85",
"temp-target" : "75,75,75,75",
"api-listen" : true,
"api-port" : "4028",
"expiry" : "120",
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"gpu-threads" : "1",
"log" : "5",
"queue" : "1",
"retry-pause" : "5",
"scan-time" : "60",
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin"

Note that I've used worksize of 128 with no negligible difference from the recommended 64.  Everything below the temp-target cgminer set, I didn't touch.

Also, at first glance, my rig with 3 GPUs that has a single core CPU, my hash rate dropped a bit when I changed the threads to single, so I put it back to two.

Hope this helps.

M

Well that's your problem right there.

Use 1 thread for p2pool.

gpu threads 5 is not a good idea with p2pool as it takes 5 times longer to complete any work. On the other hand I doubt dropping your intensity below 8 will improve your reject rate any further either. Intensity 8 is 8.3 million hashes and at 600-700 mhash for a 7970, they're done in 1/50th of a second. That is no longer contributing to your reject rate. High rejects are the norm with p2pool, but yours is higher than normal, and perhaps it's just your p2pool setup and delays elsewhere.

Nope

"intensity" : "6",
"gpu-threads" : "5"


10.54% reject

Try dropping your Intensity to 6.

I have five 7970s. I have been running them in various pools without any problems, they get a high hashrate and tiny reject rate.

However, I would really prefer to be on p2pool, but I consistently get huge reject rates.

My normal cgminer settings include:
intensity: 9
threads: 5


Per the cgminer thread I adjusted intensity to 8 and threads to 1, but still get a massive reject.

I've played with those numbers randomly, but the reject rate is always high.

Is there something stupid I'm missing?

Bounty to the first person to get it fixed.