It's odd, after a PC Tech installed some "Antec Formula 7" on my Hp Z400 Xeon (W3565) the cpu load (which is temperature throttled at 71C) went from 20-35% to 73-85%. Which is impressive!

But my twin GTX 750Ti's have dropped from 99% pegged to 83-93% according to "TechPowerup GPU-Z."

I have started getting Cuda 50's again. So I took a look at the .cfg.sample and created a mcuda*.cfg file with this.

processpriority = normal "abovenormal" is recommended for dedicated crunching machines. Since that is all this is doing right now I guess I will have to try that next.
pfblockspersm = 8
pfperiodsperlaunch = 200


I am running two processes per cpu. I have upped the cpu / process from 0.34 to 0.5 in the ap_confi.xml file.

<app_config>
<app>
<name>setiathome_v8</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.5</cpu_usage>
</gpu_versions>
</app>
</app_config>
<app_config>
<app>
<name>astropulse_v7</name>
<max_concurrent>1</max_concurrent>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>1</cpu_usage>
</gpu_versions>
</app>
</app_config>

I have changed the mb_command etc. back to the most aggressive version that someone gave me. eg.

-use_sleep_ex 60 -sleep_quantum 5 -high_prec_timer -high_perf -tune 1 64 1 4 -tune 2 64 1 4 -period_iterations_num 15 -sbs 384 -spike_fft_thresh 4096 -oclfft_tune_gr 256 -oclfft_tune_lr 16 -oclfft_tune_wg 256 -oclfft_tune_ls 512 -oclfft_tune_bn 64 -oclfft_tune_cw 64 -hp

-------------------------------------------------------------------------------------------------
So what am I missing? Is it simply my work unit loads have changed to Cuda 50?

---

A proud member of the OFA (Old Farts Association).

have started getting Cuda 50's again. So I took a look at the .cfg.sample and created a mcuda*.cfg file with this.

processpriority = normal "abovenormal" is recommended for dedicated crunching machines. Since that is all this is doing right now I guess I will have to try that next.
pfblockspersm = 8
pfperiodsperlaunch = 200

--------------------------------------------------------------------------------------------------
So what am I missing? Is it simply my work unit loads have changed to Cuda 50?

After this post I caught one GPU running a "SOG" (99%) and the other running a couple of Cuda50's (83%) and there was a difference in the GPU loads as reported by the GPU app. So I am going with the "difference" in data/application executable theory.

So the next question is what can I do to raise the GPU loading (and presumably speed up the Cuda 50 processing?).

Thanks,

---

A proud member of the OFA (Old Farts Association).

So the next question is what can I do to raise the GPU loading (and presumably speed up the Cuda 50 processing?).

[Edit:] Note, in addition to below suggestions, you may also be getting 'Shorty' (Very High Angle Range Arecibo ) tasks, which can present a lower load naturally.

Normally I would suggest a couple of instances for cuda apps, though with 750/750ti, single instance Cuda50 should be enough. So your guess of trying the processpriority key will probably help somewhat. Aside from that, any background applications such as the network streaming fruit and telemetry/diagnostics present with newer drivers [and GeForce Experience] can impact that loading under Cuda. There are guides around on the internet for disabling much bloat there. The reasons OpenCL should be less impacted there would be that OpenCL is wired in at a lower level than cuda, and is written to 'spread' more anyway. Probably future applications will have some more intuitive loading controls (and similarly conservative defaults), but for now getting the best out a particular GPU can be a matter of trial and error.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

[Edit:] Note, in addition to below suggestions, you may also be getting 'Shorty' (Very High Angle Range Arecibo ) tasks, which can present a lower load naturally.

Normally I would suggest a couple of instances for cuda apps, though with 750/750ti, single instance Cuda50 should be enough.

Ok, I'm ignorant, is that something I can do in the MCuda*.txt file?

Aside from that, any background applications such as the network streaming fruit and telemetry/diagnostics present with newer drivers [and GeForce Experience] can impact that loading under Cuda. There are guides around on the internet for disabling much bloat there. ...but for now getting the best out a particular GPU can be a matter of trial and error.

I have just uninstalled GE Experience and the two 3D drivers because I don't do gaming on this system at all. I then followed the links and found out about Microsoft's "autorun" downloaded/ran that, and all the telemetry appears to already be gone. Maybe I am running an older version. I dunno. Thanks for the pointers to bloatware though.

Thank you.
Tom

---

A proud member of the OFA (Old Farts Association).

Normally I would suggest a couple of instances for cuda apps, though with 750/750ti, single instance Cuda50 should be enough.

Ok, I'm ignorant, is that something I can do in the MCuda*.txt file?

Nah, number of instances for a given application is controlled via Boinc's optional app_config.xml file. Someone else will have to chime in with what to put in there for the various applications, just because I use an older Boinc version, and so different methods myself (on the one machine I run multi instance anyway)

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Nah, number of instances for a given application is controlled via Boinc's optional app_config.xml file. Someone else will have to chime in with what to put in there for the various applications, just because I use an older Boinc version, and so different methods myself (on the one machine I run multi instance anyway)

Here are some links to start:

♦  Application Configuration
        * If you remove app_config.xml, or one of its entries, you must reset the project in order to restore the proper values.
♦  GPU running at 75%
♦  Tasks ending in errors