Quote from: daemondazz on August 10, 2013, 01:36:50 AM

Quote from: Ghost of USD on August 09, 2013, 05:36:46 PM

This is the answer.

on p2pool, load average: 0.98 0.92 0.87

vs

ozco, load average: 0.19 0.16 0.20

You do understand what the load average figures are telling you, right? It is simply a count of how many processes running on the system needed CPU time per second during that interval, it does not tell you anything at all about the actual CPU time spent servicing those processes.

Eg, if I do a

Code:

while /bin/true; do echo "."; sleep 1; done

The load average will show as 2, even though you can probably see that the actual amount of CPU time spent was likely < 0.001% ?

A high load average may be an indication of the system being CPU starved, but I'd judge "high load average" to be 10-12x the number of CPUs present in the system, depending on the type of processes the machine is running.

Of course I do.

In this case it is the cgminer process causing that load, just as ebereon suggested.

Quote from: HellDiverUK on August 09, 2013, 07:49:02 PM

Tried bfgminer? Works better for me with my little Erupters.

Thanks for the suggestion.

After a bit of tinkering, and with the help of this script http://luke.dashjr.org/tmp/code/avalonhost-raminst, I managed to get the latest bfgminer working on my Avalon.

The difference is staggering. HW error rate dropped from 0.95% to 0.58%, and cpu usage while mining on p2pool went from 90% down to 8% max.