Got it.

I'm running out the WUs now and will follow your instructions.

I currently have a 6core /12 thread i7 5820k CPU.
When BOINC runs tasks, CUDA 50/42 uses 0.748 CPUs + 1GPU and then runs 11 other WUs on the rest of the CPU threads. So there's 12 WU going on at all times.

So 'X' = 11?

Thanks!

---

Sweet. Downloading it now.

---

Got it.

I'm running out the WUs now and will follow your instructions.

I currently have a 6core /12 thread i7 5820k CPU.
When BOINC runs tasks, CUDA 50/42 uses 0.748 CPUs + 1GPU and then runs 11 other WUs on the rest of the CPU threads. So there's 12 WU going on at all times.

So 'X' = 11?

Thanks!

If you use all your cores, then the system may become slow or unresponsive. There is also the concern about overheating your system unless you have an really good CPU cooling. Start with X at 9 first. That will put 1 on the GPU and 8 on the CPU. Once you get the app_config.xml created and installed, restart BOINC. You should then have 2 GPU and 7 CPU. Keep an eye on Temps. If they stay reasonably then you can go back and edit and raise X to a higher value.

---

Ok, I'll use a lower value at first and see how she goes. I'll keep an eye out for unresponsiveness if I bump it up.

I do in fact have a crazy custom cooling loop. 600MM of AquaComputer radiators @ flow rate of 376L/hr. CPU sits @ 55C when running all cores 100% for several hours.
GPU runs 38-42C. It should increase as more of the card is used in SoG.

---

Very poor time to view the moon. No contrasts when full. I always look at the moon at crescents so you get shadows.

---

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

A proud member of the OFA (Old Farts Association)

Ok, I'll use a lower value at first and see how she goes. I'll keep an eye out for unresponsiveness if I bump it up.

I do in fact have a crazy custom cooling loop. 600MM of AquaComputer radiators @ flow rate of 376L/hr. CPU sits @ 55C when running all cores 100% for several hours.
GPU runs 38-42C. It should increase as more of the card is used in SoG.

Ha ha LOL. That amount of radiator should suffice. And yes, the SoG app at two tasks per WILL work the card harder.

---

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

A proud member of the OFA (Old Farts Association)

I agree, I like seeing the shadows as well. Gives perspective to how tall the craters are. It also allows me to not use a moon filter because anything close to a full moon blasts a lot of light through a 14" scope. Moon filters also remove some of the colors. I guess to be silly, you could wear sunglasses at night like the Blues Brothers.
https://www.youtube.com/watch?v=gvKs2VLmVnY

Full blinding moon or not, tonight was about spending time on the scope with the wife. Astrophotography can wait till another night.

---

Went with a value of 9 for X.

Got SoG WU's now, but it wont run the opencl_nvidia_SoG WU. Says "waiting to run" or "postponed", then cycles back and forth.
Running 11 CPU WU and one CPU+GPU Unit.

"Postponed (0.04 CPUs + 1 NVIDIA GPU) - Old value used to be 0.7"

I placed the app_config.xml file into: BOINC DATA/projects/setiathome.berkeley.edu


<app_config>
<app_version>
<app_name>setiathome_v8</app_name>
<plan_class>opencl_nvidia_SoG</plan_class>
<avg_ncpus>1</avg_ncpus>
<ngpus>0.5</ngpus>
<cmdline>-sbs 1024 -period_iterations_num 1 -high_perf -hp -high_prec_timer -tt 1500</cmdline>
</app_version>
<app_version>
<app_name>astropulse_v7</app_name>
<plan_class>opencl_nvidia_100</plan_class>
<avg_ncpus>1</avg_ncpus>
<ngpus>1</ngpus>
<cmdline>-unroll 68 -oclFFT_plan 256 16 256 -ffa_block 12288 -ffa_block_fetch 6144 -tune 1 64 4 1 -tune 2 64 4 1</cmdline>
</app_version>
<project_max_concurrent>9</project_max_concurrent>
</app_config>


For App v8, should I set it to:
<avg_ncpus>1</avg_ncpus>
<ngpus>1</ngpus>


I also see this in the readme file for lunatics:
High end cards x8x x80TI Titan / Titan Z
-sbs 384 -spike_fft_thresh 4096 -tune 1 64 1 4 -oclfft_tune_gr 256 -oclfft_tune_lr 16 -oclfft_tune_wg 256 -oclfft_tune_ls 512 -oclfft_tune_bn 64 -oclfft_tune_cw 64 (*requires testing)


Thanks!

---

When you created the xml file did you use notepad then when you save it, click Save as then in the change it to all files and then the make sure when it's saved that it's actually .xml and not .xml.txt

From what you posted with 11 CPU and 1 waiting, it's not reading the app_config.xml Otherwise it would only run 9. Can you post the first 30 lines from the event log after you restart boinc?

---

Yep... It's official, I'm retarded. File had .txt after it under the properties section. Fixed that. now it shows correctly.

Thank you..

---

Glad to hear you got it straighten out.

Happy Crunching....

Z

---

Tasks now show as Anonymous platform.
Hopefully the right applications have been selected.

---

Grant
Darwin NT

Tasks now show as Anonymous platform.
Hopefully the right applications have been selected.

Noticed there are 9 errors while trying to use OpenCl. Haven't see any other work units so not sure what is going on.

---

Seems like you may be right. I can't get WU to run on GPU. Just bounces from postponed to waiting. Had a few GPU WU in the que, all failed with computer errors. only one GPU WU left to play with.
Playing with command line settings randomly found on the forums and in readme files. I even tried 2CPU and one GPU. Fail.
1CPU and .5GPU = Fail

I'm going to bed.

---

I'd turn it off for tonight and start again in the morning, that way it won't try to keep downloading tasks

I think I might have found the problem, seems like it might be the same even though the system talked about is linux. Read this tomorrow and give it a try and see if it helps.


https://setiathome.berkeley.edu/forum_thread.php?id=80847&postid=1841797

---

You still might have a corrupted opencl.dll. Though I think the first thing I would do is delete all the old wisdom files. If they were created with the corrupted dll, then that could be the problem. Same goes for the Compute Cache which contains the graphics driver kernel primitives. If the cache was created with the corrupt dll anything is possible for failures. I would delete everything in the directory and let the app and drivers recreate it when you reboot and restart crunching. On Windows the Compute Cache is located here:

C:\Users\your user name\AppData\Roaming\NVIDIA\ComputeCache

---

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

A proud member of the OFA (Old Farts Association)

Ahh now i understand why my GPU is now crunching as a Roadrunner :)

SoG ( what ever the acronym means ) in the task list :)

SignalsonGpu

Thanks :)

Btw what setup you have to get 1.6+ Million RAC

Ahh now i understand why my GPU is now crunching as a Roadrunner :)

SoG ( what ever the acronym means ) in the task list :)

SignalsonGpu

Thanks :)

Btw what setup you have to get 1.6+ Million RAC

He's running Linux with the Cuda Special App. Most of his machines have at least 4 GPUs.

---

Ahh now i understand why my GPU is now crunching as a Roadrunner :)

SoG ( what ever the acronym means ) in the task list :)

SignalsonGpu

Thanks :)

Btw what setup you have to get 1.6+ Million RAC

He's running Linux with the Cuda Special App. Most of his machines have at least 4 GPUs.

MOST of my machines have 3 GPUs. Only two have 4 GPUs. Lowest performance cards are GTX 1070's with one new Turing GTX 2080 in 3 hosts.

---

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

A proud member of the OFA (Old Farts Association)

I was thinking the same thing re the wisdom feature.
I was reading up on the wisdom feature last night before I went to bed. Seems like it learns the first run in a basic way, then fine tunes itself on the second run.
I was unaware of the Compute Cache, thank you for alerting me to that as well.

I'm tired, didn't sleep well, I literally dreamed of having problems with SETI and my PC in general. Well, maybe that's more of a nightmare than a dream. LOL

I have some Web designing to do, but I'll get back on the SETI horse later today.

Thanks again for the help.

---