B-B-R-O-Y-G-B-V-G-W lol :) I only know the R version, never heard a G version.

Big Ben rings out: "Young girls buy Volkswagens, George Washington!" is one. It's strange how memory works... it's such a ridiculously meaningless sentence, yet I saw it only once as a child and never forgot it.

B-B-R-O-Y-G-B-V-G-W
"Betty Brown runs over your garden, but Violet Grey walks" is the G-rated version I learned.

Hi Keith,

Back in high school, in the 60s, I took an electronics class. I built a tube type AM radio that actually worked. My dad told me about the resistor color code and said it like this:

"Bad Boys R___ Our Young Girls Behind Victory Garden Walls"

He never told me a G rated version. lol :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

With the 2080 Ti, you should install the 0.98b1 CUDA101 application as that would work better than the stock CUDA90 application that is provided in the app_info. The application is already in the project directory. All you need to do is a Find and Replace with the Text Editor in the app_info for the CUDA101 appname for the CUDA90 appname.

You will have to have at least the 418 series Nvidia drivers to use the application. Don't see any finished and reported work yet so can't tell if you have already done that. The instructions are in the /Docs directory.

I tried to switch to the 101 but now the gpu seem to be much quieter. Did I do it correctly?

+-----------------------------------------------------------------------------+
| NVIDIA-SMI 418.74 Driver Version: 418.74 CUDA Version: 10.1 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce RTX 208... On | 00000000:19:00.0 Off | N/A |
| 52% 55C P2 196W / 250W | 1388MiB / 10989MiB | 41% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce RTX 208... On | 00000000:1A:00.0 Off | N/A |
| 59% 58C P2 169W / 250W | 1386MiB / 10989MiB | 51% Default |
+-------------------------------+----------------------+----------------------+
| 2 GeForce RTX 208... On | 00000000:67:00.0 Off | N/A |
| 62% 60C P2 138W / 250W | 1386MiB / 10989MiB | 46% Default |
+-------------------------------+----------------------+----------------------+
| 3 GeForce RTX 208... On | 00000000:68:00.0 On | N/A |
| 62% 60C P2 162W / 250W | 1594MiB / 10986MiB | 57% Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 14819 C ...41p_V0.98b1_x86_64-pc-linux-gnu_cuda101 1377MiB |
| 1 14820 C ...41p_V0.98b1_x86_64-pc-linux-gnu_cuda101 1375MiB |
| 2 14823 C ...41p_V0.98b1_x86_64-pc-linux-gnu_cuda101 1375MiB |
| 3 1276 G /usr/lib/xorg/Xorg 114MiB |
| 3 1491 G /usr/bin/gnome-shell 98MiB |
| 3 14824 C ...41p_V0.98b1_x86_64-pc-linux-gnu_cuda101 1375MiB |
+-----------------------------------------------------------------------------+

You are running the CUDA101 application now. But still not using all of the capability of the cards. You need to add the -nobs parameter to the <cmdline></cmdline> statement in the app_info for the CUDA app version section. That will allow the CUDA thread to use an entire cpu thread to support the task. It will shave off another 5 seconds or so of compute time. The compute_time and the run_time will then match up in the stderr.txt output for each task. It will drive the utilization up on the cards and they will run a lot closer to the 250W TDP of the card. I hope you have enough power supply and cooling to handle that. You can also restrict the power usage of the cards via nvidia-smi and take the power usage down to 225 or 215W and it won't affect the crunch time all that much.

---

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

A proud member of the OFA (Old Farts Association)

If you are just trying to download the All-in-One installer, you don't need to sign into Crunchers Anonymous for that. Here is the direct download link.
http://www.arkayn.us/lunatics/BOINC.7z

If you still want to register for CA, then the last time I registered it was a simple process. But that was before the website blew up and had to be rebuilt. You might want to shoot Arkayn https://setiathome.berkeley.edu/show_user.php?userid=281426 a PM and ask if registration is still open and working.

Thank you got a new toy to play with:
ID: 8741496
Details | Tasks
Cross-project stats:
BOINCstats.com Free-DC lambda-quad home 0.00 0 7.9.3 GenuineIntel
Intel(R) Core(TM) i9-7920X CPU @ 2.90GHz [Family 6 Model 85 Stepping 4]
(24 processors) [4] NVIDIA GeForce RTX 2080 Ti (4095MB) driver: 418.74 OpenCL: 1.2 Linux Ubuntu
Ubuntu 18.04.2 LTS [4.18.0-25-generic|libc 2.27 (Ubuntu GLIBC 2.27-3ubuntu1)] 28 Jun 2019, 12:59:33 UTC

++1!

---

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

I started moving all my crunches to Linux. Lots to learn. But thank you guys for the help and support. Much appreciated

---

You haven't added the -nobs parameter yet to your cmdline statement. That will speed the crunch times up quite a bit.

---

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

A proud member of the OFA (Old Farts Association)

You haven't added the -nobs parameter yet to your cmdline statement. That will speed the crunch times up quite a bit.

There is still something else slowing his machine down. I checked his runtimes https://setiathome.berkeley.edu/workunit.php?wuid=3458788392 <- this WU is validated against my linux box and it suggests my 2060 is 25 seconds faster than his 2080 ti.
I know my test version cuda 10.0 app is 5-7% faster than 10.1 but that 30% speed difference should be other way around.

He could be overcommitted on cpu tasks and not giving the gpu thread enough time slices. The -nobs parameter will fix that. The other possibility is he doesn't have enough power supply to support 4 X 250 watts of RTX 2080Ti's. He could be overheating them too if he doesn't have enough cooling. The gpu clocks could be way down if power or thermal limited.

---

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

A proud member of the OFA (Old Farts Association)

You haven't added the -nobs parameter yet to your cmdline statement. That will speed the crunch times up quite a bit.

Can you give me some help with this "-nobs"
Thank you

---

honestly i think with a slowdown like that, it's more than just the lack of -nobs. -nobs usually only adds a small boost, not double.

from his previous screenshot, it looks like his GPUs are only seeing 50-60% utilization. that could be because the CPU is too busy to feed them, or it could be a USB cable or riser issue (if he's using them).

elec, if you are not using any kind of risers, what CPU percentage do you have set in your preferences? if you have it set to 100%, try restricting it to 80 or 90%. you need to free up CPU resources to feed the GPUs.

from the BOINC Manager Advanced View -> Options -> Computing preferences -> Computing tab
under Usage limits: Use at most ____ % of the CPUs -> change this to 80%

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

You haven't added the -nobs parameter yet to your cmdline statement. That will speed the crunch times up quite a bit.

Can you give me some help with this "-nobs"
Thank you

First do as Ian suggests and reduce the cpu usage down to 80% so there is enough cpu support for the gpus.

The -nobs parameter gets added to the <cmdline>-nobs</cmdline> statement position in either the app_config.xml or app_info.xml. That forces the app to use a full cpu thread to support each gpu thread.

---

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

A proud member of the OFA (Old Farts Association)

The cards are directly into the motherboard pciexpress slots. The PSU is 1500watt evga.

---

ok, so ignore what i said about risers, but still reduce your CPU use like I outlined above.

did it help?

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

ok, so ignore what i said about risers, but still reduce your CPU use like I outlined above.

did it help?

Looks like it. Either/both the reduction in cpu usage or the addition of the -nobs parameter got the task time down to what a 2080 Ti should be running on the 0.98b1 CUDA101 application.

---

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

A proud member of the OFA (Old Farts Association)

yup. looks like he's back on track.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

Thanks guys
Would this special app work with dual 690s?

---

Thanks guys
Would this special app work with dual 690s?

No, you at least need a Maxwell based GPU.

Cheers.

Thanks guys
Would this special app work with dual 690s?

No, you at least need a Maxwell based GPU.

Cheers.

Would Linux have any benifits to these gpus?

---

Thanks guys
Would this special app work with dual 690s?

No, you at least need a Maxwell based GPU.

Cheers.

Would Linux have any benifits to these gpus?

Possibly. The 690's could run the SoG application but the Linux CUDA60 zi3v application may still be faster. TBar made that available at Crunchers too.
http://www.arkayn.us/lunatics/CUDA60_zi3v-Special.7z
After further thought and investigation, I don't think the 690 is capable of running the special app after all because I believe the cutoff is CC 3.5 and the 690 only has CC 3.0.

Hope someone confirms my thinking.

---

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

A proud member of the OFA (Old Farts Association)

Thanks guys
Would this special app work with dual 690s?

No, you at least need a Maxwell based GPU.

Would Linux have any benifits to these gpus?

Possibly. The 690's could run the SoG application but the Linux CUDA60 zi3v application may still be faster. TBar made that available at Crunchers too.
http://www.arkayn.us/lunatics/CUDA60_zi3v-Special.7z
After further thought and investigation, I don't think the 690 is capable of running the special app after all because I believe the cutoff is CC 3.5 and the 690 only has CC 3.0.
Hope someone confirms my thinking.

. . I thought it was cc=3.2 but either way these cards don't have it.

Stephen

:(

Well I just downloaded the archive and you are correct Stephen. From the readme:
"This App will only work on GPUs that are Compute Capability 3.2 or higher."

Which is moot because the Wikipedia entry shows there never was any card actually built with the GK20A die. The next higher capability die to be used was CC 3.5 capable. So my original post was actually accurate.

---

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

A proud member of the OFA (Old Farts Association)