I had two two good reasons to implement an option for low CPU use

-My (t)rusty old AMD Phenom II X6 1055T processor has a TDP of 125 Watts. It was getting loaded 75-80% when my various GPUs were mining at 900 kHash in total. I rather save 100 Watts from my power bill, thanks

-my new mining rig that I am currently building will mine at nearly 1.5MHash/s and it only has a weak dual core i3 processor. So I had to make sure the CPU load is low.

Those who don't like the -H 2 in the 2013-12-10 build can still specify -H 0 or -H 1  

been using this to mine with my 550 gtx ti, getting around 72khs

is this good or bad? should i change any settings

...And now something about weird things on my GTX 570 and GTX 760 rigs:

GTX 570
- Most people claim that system RAM has little or no difference in hashrates, but I have suffered serious problems when i left just 2GB on mobo. These problems started immediately after cudaminer start, because the good-old config (posted in previous post) was NOT WORKING at all! F15x16 could be executed just to start the mining, but with "wrong detection" of over 600KH/s and errors on every single share ("not validated on CPU"). Auto config was giving different setups every time, rates dropped to ~200KH/s, and what is most interesting, auto config was reporting MAX WARPS: 171 (instead of 264 reported with 4GB of RAM)?! My rig was going too WILD and unpredictable for the stuff that is "not so much RAM dependent"!
- My max of ~255 KH/s can be achieved ONLY if browser (chrome in my case) is active BEFORE starting cudaminer.exe, and some page is opened (usually my pool page). After starting cudaminer, I can close everything and hashrate stays the same. Otherwise, same settings without browser give me only ~235 KH/s?!
- Some people were using Kepler kernels on Fermi devices (in previous versions of cudaminer), but at my place it was making a serious drop in KH/s
- Just to note... interactive mode (-i 1) is taking away 7-8KH/s on this rig

GTX 760
- As I mentioned before, auto never reaches the best manual config for me (and there is a better config than my current one for sure), and the auto option is changing config very often (I had like 3 different configs on 5 cudaminer restarts)?!
- This GPU (or whatever) is varying MUCH more in hashrates (160-177KH/s up-down most of the time), than GTX 570 which has pretty much "fixed" rates 252-255KH/s!

BOTH
- Is it possible that I NEVER get better hashrates on any config with 32bit vs 64bit? So many people (developer too) usually has better results with 32bit version, but I never even saw that for a second?! (not complaining, just asking...)

What i posted earlier were the GPUZ readings. Anyway i ran some benchmarks for several hours and it seemed stable @1293.4 core and 1701 mem, but after about 7 hours of mining this night my rig crashed. Unfortunately i didnt run any diagnosis sofware except for GPUZ to check the temps, as i thought its stable after the benchmark results :/
I went back to 1280 core and 1700 mem for now, as i dont have time to tinker at the moment. With -l K95x2 -i 0 -H 2 it nets me ~188-190 kHash/s, still better than 160 kHash/s...

guys help me out here

what is the best setting with my GT610 and put in some CPU i have a quad core 2 Q6600
please help me out for optimal settings cudaminer

google cpuminer proxy. or just follow that link.

https://bt.irlbtc.com/view/63689.0

this requires that you use the getwork protocol, not stratum.  So your pool URL must start with a http:// , not stratum+tcp://

The link is cpumining. I use cudaminer. There is a parameter:
-x

but I do not know how syntax for this is.

guess what cudaminer was derived from. That HTTP_PROXY environment variable should still work


now looking at that -x or --proxy switch. It appears the code accepts various socks URLs, as well as plain http:// proxy URLs. I did not write that proxy code though and never used it myself, it is taken straight from cpuminer.  Its typical use might look like this, in addition to all the  other command line options for specifying the (http!) pool URL for the getwork protocol.


I do not know enough about the socks protocol to confirm whether or not it would support a stratum connection. You can try, but you also need to have access to a socks proxy that would permit connections on the stratum port.

The first thing I would do check is the power savings settings. You're most likely using windows (the gaming gave it away :p) and I wouldn't be completely surprised if windows doesn't recognize an app running in the console as a priority, given a conservative power savings profile.

I'd double down on power saving settings, since IIRC, Chrome is hardware accelerated by default on most machines.