Apparently its Linux and he might be running that "secret sauce" Gpu app :( The one that can't be ported directly to windows because of major differences in the OS video drivers.

The only reason it hasn't been is there's no one around to do it (Jason G can, but he's busily working on a system that allows an application to be ported to the 3 major platforms (Windows, Linux, Apple) in one go, as well as a change in jobs- so his available time is more limited than usual).

---

Grant
Darwin NT

I installed the latest version of BOINC, and then went to Mikes Worlds and got the beta 6 SOG and installed it too. Restarted BOINC and here is my event log:
------
Anything look unhappy, and what was it you mentioned about using notepad and find/replacing things? It's been a while since I have had to install this. Thanks!

Al,
There is a later version of the gpu SOG task available from Mike's World. r3557 is the current one. A slightly better (results) app is r3584. Download and unpack it into a staging location. Then copy everything but the mb*sog.txt file into the main Seti directory. You will want to keep your current mb*sog.txt so this won't delete it.

Probably would be safest to stop Boinc/Seti. Then use notepad to search and replace all r3557's with r3584 in "app_info.xml". Save. Restart Boinc/Seti. The near term result should be invisible. But here is an thread with an explanation

https://setiathome.berkeley.edu/forum_thread.php?id=81596 About what the r3584 does better.

There is a discussion on getting the most out of your Gtx 1060 at https://setiathome.berkeley.edu/forum_thread.php?id=81516
HTH,
Tom

Thanks Tom, went back and got the r3584 version, had to DL 7z as well as it isn't a .zip file, windows native unzipper in 7 doesn't recognize it, but no big deal, got er done. Took a look in the mbsog.txt file in both the new DL and the current on in the directory, they are both 0 bytes so I presumed that it was ok to copy the r3584 one as well (same file name, so no biggie?) If not let me know. Also, should there be actually something in that file? My guess is yes, it must not auto populate when it is installed, but then, I haven't run one task yet with this new setup, is that what might be needed? To start letting BOINC start processing tasks, and then it would populate that file? Or do I have to do that myself? I see in the app_info the lines <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus>, something tells me I need to tweak those to assign more of a core to each task that is running, correct? It's been a while... Oh, and below is a snippet of my app_info file, has what appears to be many of hopefully the pertinent parts, without copying the whole file here, and above that is the event log of course, after starting BOINC up after copying the files over (no apparent errors, yay!):

7/15/2017 3:34:36 PM | | Starting BOINC client version 7.6.33 for windows_x86_64
7/15/2017 3:34:36 PM | | log flags: file_xfer, sched_ops, task
7/15/2017 3:34:36 PM | | Libraries: libcurl/7.47.1 OpenSSL/1.0.2g zlib/1.2.8
7/15/2017 3:34:36 PM | | Data directory: C:\ProgramData\BOINC
7/15/2017 3:34:36 PM | | Running under account user
7/15/2017 3:34:37 PM | | CUDA: NVIDIA GPU 0: GeForce GTX 1060 6GB (driver version 384.76, CUDA version 9.0, compute capability 6.1, 4096MB, 3044MB available, 4762 GFLOPS peak)
7/15/2017 3:34:37 PM | | CUDA: NVIDIA GPU 1: GeForce GTX 1060 6GB (driver version 384.76, CUDA version 9.0, compute capability 6.1, 4096MB, 3044MB available, 4762 GFLOPS peak)
7/15/2017 3:34:37 PM | | OpenCL: NVIDIA GPU 0: GeForce GTX 1060 6GB (driver version 384.76, device version OpenCL 1.2 CUDA, 6144MB, 3044MB available, 4762 GFLOPS peak)
7/15/2017 3:34:37 PM | | OpenCL: NVIDIA GPU 1: GeForce GTX 1060 6GB (driver version 384.76, device version OpenCL 1.2 CUDA, 6144MB, 3044MB available, 4762 GFLOPS peak)
7/15/2017 3:34:37 PM | SETI@home | Found app_info.xml; using anonymous platform
7/15/2017 3:34:37 PM | | Host name: ZeeCruncher
7/15/2017 3:34:37 PM | | Processor: 24 GenuineIntel Intel(R) Xeon(R) CPU E5649 @ 2.53GHz [Family 6 Model 44 Stepping 2]
7/15/2017 3:34:37 PM | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 cx16 sse4_1 sse4_2 popcnt aes syscall nx lm vmx smx tm2 dca pbe
7/15/2017 3:34:37 PM | | OS: Microsoft Windows 7: Professional x64 Edition, Service Pack 1, (06.01.7601.00)
7/15/2017 3:34:37 PM | | Memory: 47.98 GB physical, 95.97 GB virtual
7/15/2017 3:34:37 PM | | Disk: 1.82 TB total, 1.71 TB free
7/15/2017 3:34:37 PM | | Local time is UTC -5 hours
7/15/2017 3:34:37 PM | | Config: event log limit disabled
7/15/2017 3:34:37 PM | | Config: use all coprocessors
7/15/2017 3:34:37 PM | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID 7995769; resource share 100
7/15/2017 3:34:42 PM | SETI@home | General prefs: from SETI@home (last modified 03-Apr-2013 23:59:56)
7/15/2017 3:34:42 PM | SETI@home | Computer location: home
7/15/2017 3:34:42 PM | SETI@home | General prefs: no separate prefs for home; using your defaults
7/15/2017 3:34:42 PM | | Preferences:
7/15/2017 3:34:42 PM | | max memory usage when active: 24567.61MB
7/15/2017 3:34:42 PM | | max memory usage when idle: 46678.46MB
7/15/2017 3:34:42 PM | | max disk usage: 100.00GB
7/15/2017 3:34:42 PM | | (to change preferences, visit a project web site or select Preferences in the Manager)

<app_version>
        <app_name>astropulse_v7</app_name>
        <version_num>701</version_num>
        <platform>windows_intelx86</platform>
       	<cmdline></cmdline>
        <file_ref>
            <file_name>AP7_win_x64_SSE3_CPU_r2692.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3-3-4_x64.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>ap_cmdline_win_x64_SSE3_CPU.txt</file_name>
            <open_name>ap_cmdline.txt</open_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>astropulse_v7</app_name>
        <version_num>700</version_num>
        <platform>windows_x86_64</platform>
       	<cmdline></cmdline>
        <file_ref>
            <file_name>AP7_win_x64_SSE3_CPU_r2692.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3-3-4_x64.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>ap_cmdline_win_x64_SSE3_CPU.txt</file_name>
            <open_name>ap_cmdline.txt</open_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>astropulse_v7</app_name>
        <version_num>700</version_num>
        <platform>windows_intelx86</platform>
       	<cmdline></cmdline>
        <file_ref>
            <file_name>AP7_win_x64_SSE3_CPU_r2692.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3-3-4_x64.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>ap_cmdline_win_x64_SSE3_CPU.txt</file_name>
            <open_name>ap_cmdline.txt</open_name>
        </file_ref>
    </app_version>
    <app>
        <name>setiathome_v8</name>
    </app>
    <file_info>
        <name>MB8_win_x64_SSE3_VS2008_r3330.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>libfftw3f-3-3-4_x64.dll</name>
	<executable/>
    </file_info>
    <file_info>
 	<name>mb_cmdline_win_x64_SSE3_VS2008.txt</name>
    </file_info>
    <app_version>
        <app_name>setiathome_v8</app_name>
        <version_num>800</version_num>
        <platform>windows_x86_64</platform>
        <api_version>7.5.0</api_version>
        <file_ref>
            <file_name>MB8_win_x64_SSE3_VS2008_r3330.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3-3-4_x64.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>mb_cmdline_win_x64_SSE3_VS2008.txt</file_name>
            <open_name>mb_cmdline.txt</open_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_v8</app_name>
        <version_num>800</version_num>
        <platform>windows_intelx86</platform>
        <api_version>7.5.0</api_version>
        <file_ref>
            <file_name>MB8_win_x64_SSE3_VS2008_r3330.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3-3-4_x64.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>mb_cmdline_win_x64_SSE3_VS2008.txt</file_name>
            <open_name>mb_cmdline.txt</open_name>
        </file_ref>
    </app_version>
    <app>
        <name>setiathome_v8</name>
    </app>
    <file_info>
        <name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>libfftw3f-3-3-4_x86.dll</name>
	<executable/>
    </file_info>
    <file_info>
        <name>MultiBeam_Kernels_r3584.cl</name>
    </file_info>
    <file_info>
        <name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</name>
    </file_info>
    <app_version>
        <app_name>setiathome_v8</app_name>
        <version_num>819</version_num>
        <platform>windows_intelx86</platform>
        <api_version>7.5.0</api_version>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <plan_class>opencl_nvidia_SoG</plan_class>
        	<cmdline></cmdline>	
	<coproc>
            <type>CUDA</type>
            <count>.3</count>
        </coproc>
        <file_ref>
            <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3-3-4_x86.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>MultiBeam_Kernels_r3584.cl</file_name>
        </file_ref>
        <file_ref>
            <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name>
            <open_name>mb_cmdline.txt</open_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_v8</app_name>
        <version_num>820</version_num>
        <platform>windows_intelx86</platform>
        <api_version>7.5.0</api_version>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <plan_class>opencl_nvidia_SoG</plan_class>
        	<cmdline></cmdline>	
	<coproc>
            <type>CUDA</type>
            <count>.3</count>
        </coproc>
        <file_ref>
            <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3-3-4_x86.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>MultiBeam_Kernels_r3584.cl</file_name>
        </file_ref>
        <file_ref>
            <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name>
            <open_name>mb_cmdline.txt</open_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_v8</app_name>
        <version_num>812</version_num>
        <platform>windows_intelx86</platform>
        <api_version>7.5.0</api_version>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <plan_class>opencl_nvidia_SoG</plan_class>
        	<cmdline></cmdline>	
	<coproc>
            <type>CUDA</type>
            <count>.3</count>
        </coproc>
        <file_ref>
            <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3-3-4_x86.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>MultiBeam_Kernels_r3584.cl</file_name>
        </file_ref>
        <file_ref>
            <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name>
            <open_name>mb_cmdline.txt</open_name>
        </file_ref>
    </app_version>

---

Well, I opened the floodgates, let those tasks start pouring in, and she's all full up. Figures that they are mostly Guppis, I missed the AP flood earlier this week. :-/

Oh well, checking it out, with the cover off, running 3 tasks per card currently, one card is running at about 46, and the other one is at 61c., that is probably the upper one that is partially blocked by the lower one, though I do have a piece of rubber between them to spread them apart slightly, so that card can breath better. The CPU temps are ranging between 71 and 77 degrees C, pretty d@mn hot for my tastes, but not out of line for this system it appears. Going to let it go for a bit and see if I can see anything unusual happen, as well as monitoring the new power cable splitter.

---

Oh well, checking it out, with the cover off, running 3 tasks per card currently

Why?
For low end hardware, 1 task per GPU is best with SoG if you want to do as much work per hour as possible.
app_config.xml allows you to reserve a CPU core per GPU WU for best performance, without the likely hood of trashing your cache if you mess up in app_info.xml.

<app_config>
<app>
<name>setiathome_v8</name>
<gpu_versions>
<gpu_usage>1.00</gpu_usage>
<cpu_usage>1.00</cpu_usage>
</gpu_versions>
</app>

And some values such as the ones below in mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt should help get more from the cards than the defaults.
-hp -period_iterations_num 1 -sbs 1024 -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

---

Grant
Darwin NT

Took a look in the mbsog.txt file in both the new DL and the current on in the directory, they are both 0 bytes so I presumed that it was ok to copy the r3584 one as well (same file name, so no biggie?) If not let me know. Also, should there be actually something in that file? My guess is yes,

Yes, you will want something in the mb*sog.txt file. And a comprehensive discussion of "getting the most bang for your buck for a Gtx 1060" topic was started by yours truly and the people who know and understand this stuff offered all sorts of useful advice and commentary. https://setiathome.berkeley.edu/forum_thread.php?id=81516

The final summaries are, for a system you want to be able to use (eg. no lag issues)(the thread says) use this:

 -sbs 1024 -period_iterations_num 10 -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

So far the evidence is for the 1060 you should be running a single task per card for SOG and apparently 2 tasks per card for Astropulse.

If you want to dedicate/maximize production (the thread says)

-tt 1500 -sbs 1024 -period_iterations_num 4 -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

plus experiment with -hp and -high_perf -high_prec_timer

The last three items are almost guaranteed to make the system extremely laggy but are supposed to help squeeze the last drops of performance out of the gpus.



Your app_config.xml probably should look like this:

<app_config>
<app>
<name>setiathome_v8</name>
<gpu_versions>
<gpu_usage>1.0</gpu_usage>
<cpu_usage>1.0</cpu_usage>
</gpu_versions>
</app>
<app>
<name>astropulse_v7</name>
<gpu_versions>
<gpu_usage>0.50</gpu_usage>
<cpu_usage>1.0</cpu_usage>
</gpu_versions>
</app>
</app_config>

Your ap*.txt file should probably look like this:

-use_sleep -unroll 18 -oclFFT_plan 256 16 256 -ffa_block 16384 -ffa_block_fetch 8192 -tune 1 64 8 1 -tune 2 64 8 1 

HTH,
Tom

---

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

When in doubt, go with Grant. He was one of the main experts in the "bang for buck" thread. Compared to the 1080 type cards, the 1060 is "low end" or at best "mid ranged".

My own limited experience with trying 2 tasks on a 1060 is it was slower over all than with 1 task.

Tom

---

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

When in doubt, go with Grant. He was one of the main experts in the "bang for buck" thread.

Mike's the expert.
Those are just the values I found best on my GTX 1070s (daily use system) and GTX 750Tis (dedicated cruncher).

EDIT- for GTX 1060 performance for given command line values, check out Wiggo's main systems.

---

Grant
Darwin NT

EDIT- for GTX 1060 performance for given command line values, check out Wiggo's main systems.

The parameters I posted above are from Wiggo's main systems, copied from the "bang for a buck" thread.

Tom

---

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

Mike's the expert.
Those are just the values I found best on my GTX 1070s (daily use system) and GTX 750Tis (dedicated cruncher).

Grant,
I find myself with 2 Gtx 750 Ti's on some of my "other" (Z400 & Dell 7010) systems. What parameters are you using for your 750Ti? I will need to throttle them back a little but surely they are better than the basic ones for a 750 in the docs?

Or are you using these on the 750 as well as the 1070?

-hp -period_iterations_num 1 -sbs 1024 -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

Thanks,
Tom

---

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

Thanks for the head up and advice, I will take a look at it once I get back to the shop, hopefully tomorrow sometime. Before I left, felt the wires and connections, everything seemed cool enough to the touch, that I don't think I have to worry about it. The CPU temps were running 70-78, One GPU in the upper 40s and the other in the low 60s. As to the number of tasks per card, I guess I had thought that since it was a 6 gig card, with the fastest bus speed and memory bus width, as well as clock speed and core count, that they might be edging up into the mid range level cards, but that is probably just wishful thinking. It will be interesting to see how it performs till then though. And, as this is going to be a dedicated cruncher, lag isn't a huge worry for me, as long as it responds enough to at least use the mouse enough to suspend BOINC if I need to do any maintenance on it. ;-)

---

Or are you using these on the 750 as well as the 1070?

For dedicated crunching they gave the most work per hour on the GTX 750Tis, however for a daily use system it would have been unusable due to the huge screen/keyboard lag.

---

Grant
Darwin NT

Remember, HEAT kills!

I was reminded that heat seems to eat my HD's today. I had to force my Z600 to shut down due to losing connectivity with the Keyboard/Mouse via the 4 way keyboard/mouse via USB and Vga box I have.

Normally you simply shut down all connected computers, wait say 30 seconds re-boot and the USB connectivity issue goes away.

So the Dell 7010 came right up. The Z400 came up reluctantly (I have been trying to run a GT 720 and a GTX 750Ti in it) and through a "driver restart" for the first time in I don't know how long. I promptly took the -hp and -high_perform parameters out. :)

The Z600 came up, started windows and promptly said "We need to run Chkdsk on your C drive" something about something was not consistent. A couple of hours later....

Before I moved 3 HD's out of the Z400 it was running near 78C with a LCS installed on the cpu. I had added an extra fan on the front of the box too. Once I pulled out 3 HD's and put in 1 smaller HD. Plus pulled the Gtx 1060 3GB out of it, its temperature went down to about 54C.

The Z400 has regularly eaten HD's which is why I was running Raid 1 (and occasionally remembering to back it up :) I think it was simply running too hot. I didn't get the LCS heatsink installed until earlier this spring. So TThortle was running the cpu at anywhere from 30% to 60% to keep it under 71C. First it was better thermal paste (upto 78%) then it was the LCS (temp dropped to 65C when the case was clean).

So with that in mind I did three things more or less after the Chkdsk got done. 1) I turned up the fans in the bio's to 100%. It's really howling in there now. 2) I pulled the 2nd Gtx 1060 6GB out of the case. 3) I downgraded from the 20MB of registered ram down to 6 MB of ram (4 on cpu 0, 2 on cpu 1).

Its running a LITTLE cooler. If I keep this thing I need to put more muscle into finding a cheap(er) high performance cpu heatsink and greater cooling for the whole case.

I am currently running two system backups with the usb backup drives I have.

And I promptly re-listed both the Z400 and the Z600 on ebay w/o HD, Video cards or expensive registered ram.

This is all in reaction to having so much trouble finding a better non-LCS temperature reduction system and discovering that a cpu with AVX is the secret sauce to higher performing BOINC cpu tasks across all projects.

Once the backups are over I "promise" to re-measure the clearance I have for Z600 cpu heatsinks and TRY to find an aftermarket heatsink that is both short enough and cheap enough. Its that, or keep replacing equipment faster than I need to.

Hope this commentary was useful.
Tom

---

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

Will the case hold thicker fans?
If so, search for 38mm or 50mm fans.
They move A LOT more air with the same footprint.

Will the case hold thicker fans?
If so, search for 38mm or 50mm fans.
They move A LOT more air with the same footprint.

Brent,
I'm not sure exactly what you mean by "thicker". There is height, width and depth ( I think). So are you talking about wider fans or deeper fans?

Thanks,
Tom

---

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

Hi Tom, I have no idea if this will fit your motherboard, but I saw it in a JayzTwoCents video this week when he was upgrading his VR htpc:

CoolerMaster Gemini II S524 cpu cooler https://www.amazon.com/Cooler-Master-GeminII-Version-RR-G5V2-20PK-R1/dp/B00UOIK3FU/ref=sr_1_1?ie=UTF8&qid=1500426402&sr=8-1&keywords=coolermaster+gemini+cooler+s524

They even have a thinner one:

CoolerMaster Gemini II M4 https://www.amazon.com/dp/B0080ATR2Y?ref=emc_b_5_t

---

... and still I fear, and still I dare not laugh at the Mad Man!

Queen - The Prophet's Song

Deeper, thicker, meatier, whatever you want to call it.

Instead of 120mm x 120mm x 25mm, or 140mm x 140mm x 25mm, it would be x38mm or x50mm, or versions in between with some manufacturers.

I have a pair of 140mm x 38mm rated at 42 - 141 CFM. BTW do DO hurt when touched!

A way to finagle a pair of Corsair Hydro Series H110i or Hydro Series H100i v2 Extreme Performance Liquid CPU Coolers onto it? I understand they would have to run outside the case, and the issue would be getting the lines out, but with some creativity, and time, anything (well, maybe lots?) is possible. Unless you just don't want to F*#k with it any longer, which also could be understandable. Just tossing stuff out and seeing if anything sticks to the wall... ;-)

---

[quote
I have a pair of 140mm x 38mm rated at 42 - 141 CFM. BTW do DO hurt when touched![/quote]
Yep. :-{ You'll lose a fingernail if you poke a Delta 38mm or 50mm fan. From experience.

---

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

A proud member of the OFA (Old Farts Association)

I've had a couple of these Delta 120x38mm 240cfm for years now, but they scare the hell out of me just powering them up (talk about a screaming shriek, not trying to catch them), but now they have 252cfm versions. :-O

Cheers.

Yea I bet they do have quite the scream @5200 RPM.

An idea though, attach a handle and a funnel to one ... and you have a great high powered computer duster :D