Hi all,
I have now a GTX 1060 6Go and a GTX 1070 using zi3v-Cuda9.0 under Linux Fedora 27. However, the computation is not always using GPU, sometimes down to 70 %. Is there a way to improve this ? Can I run two tasks in parallel on each GPU or wil it give unreliable results?

For information, I have at this time 0 error, 0 invalid, 24 inconclusive, 626 valid and 987 pending tasks.

---

The application is not designed to support two tasks per GPU. It may work, but it may result in very much extended run times (over those for one task per GPU)

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Ok, thanks. Can I had command line options to increase GPU occupation ?

---

-nobs forces 100% CPU use, which makes sure the GPU is not waiting.
Also don't pin your CPU usage. You will want 3 or 4 free threads for the 2 GPUs.

---

Thanks Brent for this advice.
Cheers

---

I have been having trouble with the Linux r3584 SoG app hanging and the process never ending. Could be a system issue, but I wanted to try the ATi version of the r3584 Linux app before I make major changes to my system. Does it sound like a possibility that the SoG app is a contributing factor? Can someone point me to where I can download the app? Thanks!

---

GitHub: Ricks-Lab
Instagram: ricks_labs

On my older ATI GPUs r3584 always gave False overflows. The 3505 version doesn't give False overflows and is just as fast as r3584. You might try that, ATI5r3505&IntelSSSE3CPU.7z Otherwise, you might try a different GPU driver. I've been in a battle with the last version of the Special App that works in OSX Yosemite and False overflows on a GTX 750 Ti. It seems a slightly older CUDA driver may have fixed it. Strange it only happens with the 750 Ti, the GTX 9 series doesn't have the problem.

I`m running 3584 on Linux Mint 18.3 R9 380 and never had an issue nor invalid.

---

With each crime and every kindness we birth our future.

On my older ATI GPUs r3584 always gave False overflows. The 3505 version doesn't give False overflows and is just as fast as r3584. You might try that, ATI5r3505&IntelSSSE3CPU.7z Otherwise, you might try a different GPU driver. I've been in a battle with the last version of the Special App that works in OSX Yosemite and False overflows on a GTX 750 Ti. It seems a slightly older CUDA driver may have fixed it. Strange it only happens with the 750 Ti, the GTX 9 series doesn't have the problem.

Thanks TBar! I have downloaded, but this weekend I convinced my self that I have spent way too much time trying to get my Triple ProDuo block of GPU's working on my latest platform. This configuration has had issues with Zenith Extreme and X99-E-10G, but worked with no issues on the Crosshair V Formula-Z, which was its original home. I moved it back over the weekend and it has no problems. I have moved the block of 4 RX Vega64 over to my Linux cruncher only to realize that ROCm doesn't yet support X399 platform...

During the troubleshooting of the issues with this configuration, I went back and forth between 16.04.3 and 16.04.4 and AMD drivers from last quarter and the latest. I originally built it on the ASRock X399 professional with no GPU issues but had OC stability issues with it, which is why I moved it to Zenith.

---

GitHub: Ricks-Lab
Instagram: ricks_labs

I`m running 3584 on Linux Mint 18.3 R9 380 and never had an issue nor invalid.

Hi Mike, Thanks for sharing your experience for confirmation. I strongly suspect it is just the Triple ProDuo configuration that is the root of the problem. Confirmation on IG that another user with 2 ProDuo and 2 Vega64 has issues mining with all 6 GPUs on Zenith (Windows). Problem goes away by disabling one card. Getting this setup working on Zenith is a bit cludgy as it will get NVRAM error unless you bring it up with 1 card first from cleared CMOS. ASRock had no GPU issues, but just could not OC as well. Maybe Asus will have a BIOS fix, but I have been waiting 1 year for a confirmed issue I reported on C6H to be fixed, so I am not going to wait around...

---

GitHub: Ricks-Lab
Instagram: ricks_labs

Since the Old thread is LOCKED.... I started a New one, https://setiathome.berkeley.edu/forum_thread.php?id=80636&postid=1931328

So, setiathome_x41p_V0.96_x86_64-Linux_cuda9x has made it's appearance and for the first time since zi3v, it works with the Overflows.
Right now it still has trouble with the Arecibo shorties, but, at present that's not a real problem. Currently Speed improvements are in the 30 to 60% range, depending on the GPU, with the 750 Ti being around 30 % faster. Stay tuned...

BTW, if someone wants to Unlock the old thread and move this post there it would be appreciated.

i was trying v0.95 on 750ti's and it was just immediately trashing every work unit with computation errors.

v0.96 fixed this? where's the download link? your link just redirects back to your own post lol.

---

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

Hmmmm, you must have a compile from Petri, I never compiled 0.95 on Linux. After getting Hundreds of Invalids on My Macs with 0.95 I decided it wasn't worth the trouble to find my old Linux dev system. I never did get Errors with 0.95, just Every Overflow ended up invalid... except a handful that cross validated with W3Perl. I never did find my old system either, had to build another Linux dev system. I have two machines running 0.96 on Linux with 750 Ti, both work fine. I'm still trying to figure out why they hate Arecibo shorties, once that is fixed I will post a link to the fully working App.

Sounds good TBar. Will look for the app download link when it is ready for primetime.

---

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

A proud member of the OFA (Old Farts Association)

Hmmmm, you must have a compile from Petri, I never compiled 0.95 on Linux. After getting Hundreds of Invalids on My Macs with 0.95 I decided it wasn't worth the trouble to find my old Linux dev system. I never did get Errors with 0.95, just Every Overflow ended up invalid... except a handful that cross validated with W3Perl. I never did find my old system either, had to build another Linux dev system. I have two machines running 0.96 on Linux with 750 Ti, both work fine. I'm still trying to figure out why they hate Arecibo shorties, once that is fixed I will post a link to the fully working App.

is there a link for v0.96 somewhere, or should i ask petri for it? like i said, your link in your previous posts just redirects back to itself. ..

v0.95 runs fine on my 2* 1050ti machine. with a 38% speed boost vs the "normal" special app. i do see issues with invalid short tasks. no errors, just end up invalid. all on the order of <30s run times. the longer ones process just fine and validate.

v0.95 just doesnt work on 750ti's. it's not much consequence, im upgrading that sytem to dual 1060's soon enough.

and for anyone else not aware, v0.95+ requires R396+ beta nv drivers. 390 whql wont work.

---

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

Hi,

the 0.96 is still not finished. Like TBar said there are problems with Arecibo shorties. When we get them ironed out we will come up with V1.00 .

I've got two weeks summer vacation left and I hope I have time to fix the app.

Petri

---

To overcome Heisenbergs:
"You can't always get what you want / but if you try sometimes you just might find / you get what you need." -- Rolling Stones

that would be awesome. we really appreciate the effort to improve our performance!

---

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

Looking forward to the newest app. Was browsing some of Petri's tasks and came upon this one.
https://setiathome.berkeley.edu/workunit.php?wuid=3079506159

which just so happened to be run on both hosts by a 1080 card. Petri's host finished it 60 seconds faster than an older x41p_zi3t2b application. Granted an older CUDA8 app vs. CUDA9.2 app but the statically linked app is so much faster it will be nice to use eventually.

---

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

A proud member of the OFA (Old Farts Association)

@Petri, can you explain simply what the new tuning parameter in the latest 0.96 Beta does. I am referring to:

{Using default pulse Fft limit (-pfl 64)} in the stderr.txt output for a task. This seems to be a new parameter not mentioned in the original x41zi or x41p_zi3v notes.

---

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

A proud member of the OFA (Old Farts Association)

Petri did mention the -pfl flag before in https://setiathome.berkeley.edu/forum_thread.php?id=78569&postid=1944686

<snip>
Could you try with a new flag: -pfl 64
It sets a splitting point to pulse finding which one of the internal functions to use.
I find the -pfl 64 give faster run times compared to default (no flag set equals to -pfl 512). I'll change that in confsettings.cpp to 64 in the future.