How do I run GPU with high priority? I run the standard apps and have created and successfully used cc_config.xml and app_config.xml. I know very little about the codes and don't want to melt my machine. I can copy and paste very well though.

One other question, in Stderr output I have this;

OpenCL Platform Name:	 NVIDIA CUDA
Number of devices:	 8
Max compute units:	 8

I assume the number of devices, 8, is the 8 physical GPUs and max compute units, 8, is the number of WU they are to crunch. I have app_config.xml running 2 WU on each GPU, 16 total and it works great but why doesn't is show as 16 in Stderr and does it make a difference?

---

About the priority

For AP read you could use the -hp switch in your command line, read the description on the readme file suplied with the build.

For Mb you need to edit the file mbcuda.cfg the instructions how to do are in the file itself.

---

About the priority

For AP read you could use the -hp switch in your command line, read the description on the readme file suplied with the build.

For Mb you need to edit the file mbcuda.cfg the instructions how to do are in the file itself.

If you want to teach me to fish it is going to be a long cold winter and I will probably break my pole. Where is the DOS program and is it point and click like DOS7?

---

LEt´s see if i could help you with my bad english.

One at a time. Since there is no AP WU avaiable let start with MB (I asume you use the lunatics apps)

On your SETI project directory (mine is D:\Boinc\projects\setiathome.berkeley.edu) you must have this file: mbcuda.cfg

Open it with notepath and read it, there are all instructions to do what you ask for.

To rise the priority you just need to add this line (actualy just take out the ;;; in the begining of the line)

processpriority = abovenormal

Then close the file and the next MB WU started will run in the new priority. To make it work instantaneusly your need to compleately stop boinc (not just the manager) and restart.

Becareful 'abovenormal', or 'high' must be used only on crunchers only hosts or you will be experience video lag and other wierds efects.

---

Juan has provided good information.

This thread also has instructions regarding the same topic. The user named rob smith begins the explanation about half way down.

If you do it right, wait for a few tasks to complete. Then, you can look at them. Recently I set mine to "normal" priority. Therefore, when I open up the information about tasks my computer crunches, I see this line:

Priority of process set to NORMAL successfully

I'm not sure however, if you need to be running the lunatics applications for this to work. I run lunatics.

As for the second part of your question, sorry I'm unfamiliar with that.

.

LEt´s see if i could help you with my bad english.

One at a time. Since there is no AP WU avaiable let start with MB (I asume you use the lunatics apps)

One must never ass/u/me. I use the standard apps and wish to continue using them. Your English is way better than my Portuguese. The only Portuguese I know is the pet name the Brazilian women in the Ironbound section of Newark call me; Safado.

---

I´m not sure about stock apps, but check if you have the file, if yes just change it will work too. Actualy the MB stocks apps comes from the Lunatics team also.

About Compute Units you could read an explanation on: http://sa09.idav.ucdavis.edu/docs/SA09_NVIDIA_IHV_talk.pdf

---

I run mostly stock apps and the approach is pretty close to what Juan suggests. However, instead of mbcuda.cfg, you'll find separate files in your project directory for each Cuda flavor. So look for mbcuda-7.00-cuda50.cfg, etc. They're probably empty. There's a sample file for each one. Just pick one, change the first

;processpriority = abovenormal

to

processpriority = abovenormal

(just remove the semicolon). Save that file over each flavor of Cuda that you normally receive (probably just cuda50, cuda42, and cuda32). From that point on each GPU task will pick up the higher priority. Does it actually help? Well, frankly I don't think I noticed much difference on my machines. :^)

Edit: Be sure you use a text editor, like Notepad, when you edit the sample file.

I think with the stock versions of the cuda apps, you may not have mbcuda.cfg but have separate files for cuda 42, 50, etc. Don't remember the filenames but they include mbcuda and the 42, 50, etc. These can be edited with notepad.

Edit: Jeff posted first and has the info on file names.

---

Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.

.

LEt´s see if i could help you with my bad english.

One at a time. Since there is no AP WU avaiable let start with MB (I asume you use the lunatics apps)

One must never ass/u/me. I use the standard apps and wish to continue using them. Your English is way better than my Portuguese. The only Portuguese I know is the pet name the Brazilian women in the Ironbound section of Newark call me; Safado.

You will still have the mbcuda.cfg file, but it will be empty.

;;; This configuration file is for optional control of Cuda Multibeam x41zc
;;; Currently, the available options are for
;;; application process priority control (without external tools), and
;;; per gpu priority control (useful for multiple Cuda GPU systems)
[mbcuda]
;;;;; Global applications settings, to apply to all Cuda devices
;;; You can uncomment the processpriority line below, by removing the ';', to engage machine global priority control of x41x
;;; possible options are 'belownormal' (which is the default), 'normal', 'abovenormal', or 'high'
;;; For dedicated crunching machines, 'abovenormal' is recommended
;;; raising global application priorities above the default
;;;   may have system dependant usability effects, and can have positive or negative effects on overall throughput 
processpriority = high
;;; Pulsefinding: Advanced options for long pulsefinds (affect display usability & long kernel runs)
;;; defaults are conservative.
;;; WARNING: Excessive values may induce display lag, driver timeout & recovery, or errors. 
;;; pulsefinding blocks per multiprocessor (1-16), default is 1 for Pre-Fermi, 4 for Fermi or newer GPUs
pfblockspersm = 15
;;; pulsefinding maximum periods per kernel launch  (1-1000), default is 100, as per 6.09
pfperiodsperlaunch = 200

That is what I run on my 670 & 660

---

OK, thank all of you for the replays. I found the files for MB and the sample file; I can see this is not going to be as easy as just changing 1 to .5 to run two WU per GPU. Will I gain enough on a dedicated cruncher going from below normal to above to risk a Cheronobel like core meltdown?

---

The use of this switch will not meltdown your CPU don´t worry. If you find the files just take out the ; and it will work.

The major problem when you use high priority is your video response time (some slow hosts like mine presents a noticeable video lag) or if you run other jobs in your computers.

In simply language some programs not like others runing on high priority and almost stop when that happening. Thats make no diference on a crunching only hosts but in a general host is better leave without changes.

You could expect a marginal gain of 1-2% on the performace of the hosts if you set the priority to abovenormal or high. Of course YMMV.

<edit> fast GPU´s like the 690 specialy on multiGPU host like the one you have like the abovenormal and even high setting.

---

Then close the file and the next MB WU started will run in the new priority. To make it work instantaneusly your need to compleately stop boinc (not just the manager) and restart.

You don't need to restart Boinc to get the apps to use the new priority level, just suspend GPU usage via the activity menu for a moment.

Claggy

Thank all of you, I am now crunching MB GPU WU with high priority. The only way I know is Stderr output says so. I can play a HD video with SETI running 16 WU no problem too. SETI is not asking enough from these cards.

How do I do the same with AP WU? Thank you in advance.

---

Look in the file: AstroPulse_OpenCL_NV_ReadMe.txt the usage of -hp

You could see the priority with taskmgr.

You have a top CPU and aparently you don´t do any CPU work, so maybe that´s why you not experience any lag. Did you check your GPU usage and temp on each GPU?

BTW if you know about some more cheap 690 (used) please tell me, i could be interested to buy few more.

---

You have a top CPU and aparently you don´t do any CPU work, so maybe that´s why you not experience any lag. Did you check your GPU usage and temp on each GPU?

I crunch 12 CPU MB WU along with 16 GPU MB WU. My GPU usage and temps did not change. Remember this is a crunching only test machine.

High end used cares are now being grabbed by coin miners. I think they gave up on waiting for the promised mining application specific chips.

AstroPulse_OpenCL_NV_ReadMe.txt is empty??

---

I crunch 12 CPU MB WU along with 16 GPU MB WU. My GPU usage and temps did not change. Remember this is a crunching only test machine.

Sorry my mistake, i just see on your cruched WU and don´t see any CPU work.

Was you able to locate the AP file?

---

[quote]
Was you able to locate the AP file?

Yes but it is empty,0kb

---

[quote]
Was you able to locate the AP file?

Yes but it is empty,0kb

Since you're running stock and not Lunatics, I don't think you'll actually find the file that Juan mentioned. You want a file named ap_cmdline_6.04_windows_intelx86_opencl_nvidia.txt. It should be empty, but just edit it in Notepad or other text editor and create a single line with just '-hp' (without the quotes). As with the mbcuda.cfg change, there are differing opinions as to whether this makes much difference or not. I'll let the experts debate that point!

My sugestion to him is try to find the AP read.me file, there he will find all the avaiable options an instructions for each parameters so he could be choose what will be better to him.

Adding to Jeff post to guide you, as sugested to me by Mike on my 690 host i use:

-hp -unroll 12 -ffa_block 12288 -ffa_block_fetch 6144

Just copy and paste to the file mentioned by Jeff.

Works perfect here, that will give you an start, After you confirm it´s working you could modify the parameters to get an even better optimization.

---