Please post issues with v8.19 Windows GPU SETI MB apps (if any) here.
Single thread for all flavours: ATi, NV, iGPU.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

Please post issues with v8.19 Windows GPU SETI MB apps (if any) here.
Single thread for all flavours: ATi, NV, iGPU.

. . Hi Raistmer,

. . As a bit of an amateur I am waiting for Lunatics Beta5 so I can get right into it. Since 4bit WUs offer better resolution (more/better information) has anyone talked about distributing them as well?

. . Thanks for all your hard work.

Stephen

.

They run Ok on my Windows 10 PC with opencl_nvidia_SoG but they seem to use a good deal of CPU, up to 23%.Geforce GTX 750 OC.
Tullio

---

It's not subject of this thread. AFAIK Richard already works on it.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

To decrease CPU usage one can use -use_sleep option.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

It's not subject of this thread. AFAIK Richard already works on it.

And has now posted about it in the appropriate (retitled) thread.

I am back to v8 8.00, whose CPU usage is 7%.
Tullio

---

v8 8.00

So you mean CUDA or what?
http://setiathome.berkeley.edu/apps.php

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Yes, Cuda 50 on the Windows 10 PC with GTX 750 OC. Instead it is v8 8.10 on the 64-Bit Linux box with HD 7770 and v8 8.05 on the 32-bit Linux laptop with no GPU.
Tullio

---

Yesterday I started up a new machine ("woof-PC") running stock with 2 x GTX 750ti on an AMD FX-8350, 16gb of RAM, on a Gigabyte GA-990FXA-UD3 Rev 4.0 motherboard, 3 WUs/GPU. This morning I noticed that 3 WUs were running 7 or so hours and nowhere near completion (time remaining for one was ~18 hrs, and the other two > 3 days(!!)) and the machine was super-laggy. I aborted the WUs, shut down and restarted BOINC, and not so laggy anymore.

Here are the WUs:

10/15/2016 3:59:11 AM | SETI@home | task 21au09aa.14085.476.13.40.163_1 aborted by user
10/15/2016 3:59:44 AM | SETI@home | task 19ja09ad.31343.1708.15.42.156_1 aborted by user
10/15/2016 4:05:06 AM | SETI@home | task 19ja09ad.31343.1708.15.42.226_1 aborted by user

My command line is:

-sbs 512 - period_iterations_num 10 -hp


EDIT: looking at my woof-PC error WUs, I see they all ran 25,000+ secs, with maybe 17-20,000 secs CPU, essentially blocking 1/2 of my threads for doing work.

EDIT2: Also, looking in BoincTasks History, I see a few WUs that completed ok, but took 3-5 hours to run, where most run on the order of an hour or less.
What's up with that?

FWIW: no such problems on my 3 Intel machines.

---

Check if any driver restart messages in system event log.
if yes:
return period_iterations_num to 50
decrease tasks per GPU to 2.

if not:
add -cpu_lock.

Or just revert to complete default (to be more on this thread subject) and report back if default settings require correction.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

Check if any driver restart messages in system event log.
if yes:
return period_iterations_num to 50
decrease tasks per GPU to 2.

if not:
add -cpu_lock.

Or just revert to complete default (to be more on this thread subject) and report back if default settings require correction.

On FX 8350 -cpu_lock is necessity running multiple instances.
Also i suggest to run only 2 instances on the 750TI.
With 2 GPU`s running 3 instances each 6 CPU cores are in use but only 4 FPU`available.
So the app will go into stall if no FPU ressources are available.

---

With each crime and every kindness we birth our future.

I added -cpu_lock and set to 2 WUs/GPU, and that seems to have cured my problems (for now!); I should have remembered about the CPU having only 4 FPUs, but didn't.

Now WUs are well under an hour each (rather than 1+hours). We'll see if this holds up or not.

Thanks for the help!

---

I've read the current documentation and gone back through previous and can't find the answer to what I want to do. In the CUDA app, through MBCUDA.CFG you could set the app priority using -bel -nor -abo and -hp. In the OpenCL app all I've been able to do is set -hp (high_priority) for the app. That results in too much system lag and responsiveness with my aggressive settings. I want to run in above_normal (-abo) for the r3528 app. I tried the -abo tag in the r3528 819 section <cmdline></cmdline> and my stderr.txt still reports tasks running in below normal priority. I also tried to set above normal priority in cc_config.xml using the <process_priority_special>3</process_priority_special> file option. It too did not have any effect on changing the app priority level to above normal while running nor did it change the reported level in stderr.txt.

Is it possible to change the app priority level via any of BOINCs' or SETIs' file configurations?

For the while I have managed to set the app running priority to above normal via a ProcessLasso rule. The app does run in the above normal priority but the app is unaware of its raised priority level because it still writes stderr.txt output of running in below normal priority.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

OpenCL builds have only 3 priority levels (third is real-time one).
ProcessLasso can be used (or similar app) to change to any desired level.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

OpenCL builds have only 3 priority levels (third is real-time one).
ProcessLasso can be used (or similar app) to change to any desired level.

https://bitsum.com/

Keith ,I run Process Lasso.

I also run these just to see how the system runs

BOINCtasks, and SIVX64

---

Yesterday I started up a new machine ("woof-PC") running stock with 2 x GTX 750ti on an AMD FX-8350, 16gb of RAM, on a Gigabyte GA-990FXA-UD3 Rev 4.0 motherboard, 3 WUs/GPU. This morning I noticed that 3 WUs were running 7 or so hours and nowhere near completion (time remaining for one was ~18 hrs, and the other two > 3 days(!!)) and the machine was super-laggy. I aborted the WUs, shut down and restarted BOINC, and not so laggy anymore.

Here are the WUs:

10/15/2016 3:59:11 AM | SETI@home | task 21au09aa.14085.476.13.40.163_1 aborted by user
10/15/2016 3:59:44 AM | SETI@home | task 19ja09ad.31343.1708.15.42.156_1 aborted by user
10/15/2016 4:05:06 AM | SETI@home | task 19ja09ad.31343.1708.15.42.226_1 aborted by user

My command line is:

-sbs 512 - period_iterations_num 10 -hp


EDIT: looking at my woof-PC error WUs, I see they all ran 25,000+ secs, with maybe 17-20,000 secs CPU, essentially blocking 1/2 of my threads for doing work.

EDIT2: Also, looking in BoincTasks History, I see a few WUs that completed ok, but took 3-5 hours to run, where most run on the order of an hour or less.
What's up with that?

FWIW: no such problems on my 3 Intel machines.

Cruncher, that commandline was for the 980s..It has a lot more memory than the 750Ti does

-sbs is a function of how much memory the GPU has, not CPU memory. So for a 980, 980Ti, 10x0s, you can increase that number up to a max of 1024 but with lower RAM GPUs that value has to be lower.

As Raistmer said default for -period_iterations_num is 50 but with high end GPU you can decrease it down to as low as 1 (which I do for 980Ti and 1080, 1070s) But for a 750ti that is too low and best to keep it at default of 50.

Sorry, out of town so can't touch base much this weekend.

Zalster

---

@Zalster: Thanks for the clarification(s). Hope you are having fun on your trip!

Is there a writeup for command line stuff? If there isn't, there really should be, comparable to the ones for the config xml files. Since the parameters are there for general use now, us SETIzens should have one. (If I've missed it, please let me know but flame me gently, please!).

---

@Zalster: Thanks for the clarification(s). Hope you are having fun on your trip!

Is there a writeup for command line stuff? If there isn't, there really should be, comparable to the ones for the config xml files. Since the parameters are there for general use now, us SETIzens should have one. (If I've missed it, please let me know but flame me gently, please!).

I think i mentioned it once.
There should be a read me file in your project folder.
On the bottom i wrote some examples for the comand line options.

---

With each crime and every kindness we birth our future.

OpenCL builds have only 3 priority levels (third is real-time one).
ProcessLasso can be used (or similar app) to change to any desired level.

Raistmer, if I understand correctly, then you are saying that there is no built-in method of controlling priority level with BOINCs or SETI's configuration files? The limitation is built-in to the OpenCL platform?

Using ProcessLasso is doing what I want for now. I just wanted to see if I could get the process priority level correctly written to stderr.txt.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)