Bitcoin Forum

Other => Beginners & Help => Topic started by: Double_Trouble on December 21, 2013, 11:20:18 AM



Title: Only 50% CPU performance with CPUminer?
Post by: Double_Trouble on December 21, 2013, 11:20:18 AM
Hi!

I'm currently using cpuminer-2.3.2 to mine Dogecoins. I would like to ask in the official topic, but since I'm new here I have only the option to ask in this forum. My question is why cpuminer is only using about 50% of the total cpu performance.

11:03:34 AM  CPU    %usr   %nice    %sys %iowait    %irq   %soft  %steal  %guest   %idle
11:03:34 AM  all    0.03   59.73    0.04    0.02    0.00    0.00    0.47    0.00   39.71
11:03:34 AM    0    0.04   59.75    0.04    0.02    0.00    0.00    0.44    0.00   39.71
11:03:34 AM    1    0.03   59.80    0.03    0.02    0.00    0.00    0.40    0.00   39.72
11:03:34 AM    2    0.03   59.72    0.06    0.02    0.00    0.00    0.49    0.00   39.69
11:03:34 AM    3    0.03   59.65    0.04    0.02    0.00    0.00    0.55    0.00   39.72


Is there some kind of configuration that I can use, that I have missed? I'm using Debian 7.0 x64 and QEMU virtual intel CPU's.

Thanks in advance!



Title: Re: Only 50% CPU performance with CPUminer?
Post by: luqash3 on December 21, 2013, 12:48:59 PM
Double_Trouble you really seem busy in researching these performance but I guess you must even take out some time to research bitcoins future performance like in my opinion on the basis of technical it shall crash soon. So hope you consider my request of determining bitcoin price performance


Title: Re: Only 50% CPU performance with CPUminer?
Post by: bitpop on December 21, 2013, 06:59:54 PM
Add threads?


Title: Re: Only 50% CPU performance with CPUminer?
Post by: cryptoprime on December 21, 2013, 07:45:34 PM
First of all, make sure you're using the most optimized CPU miner found here:

https://github.com/palmd/quarkcoin-cpuminer
https://bitcointalk.org/index.php?topic=353448.0

Secondly, ensure the # of threads running equals the # of cores on your CPUs. The Minerd app should determine that automatically but if not, just use -t # argument to specify the # of threads to run.