There have been a rash of posts about the SoG application not running because of no OpenCL component on the system. I wonder if it has to do with the apparent two kinds of Nvidia drivers that can be downloaded now. There is the Standard version and the new DCH version. And they are not compatible with each other. Window Update is installing the DCH version and you can't then install the Standard version over the top of the Windows Update version.

I may not have any experience with the DCH version then. My custom installs that back dated the drivers using the "delete everything" check box have all been working.

I started using back-dated drivers when I started experiencing odd events like Seti running two distinct tasks on 1 gpu. And it wasn't the GPU had split in two. Basically what was happening is the driver install created "two" gpus, then Seti ran two. But the task manager only recognized one. I have had that happen twice on two new different Windows 10 machines.

I haven't tried to reinstall the same version number of any Nvidia driver that didn't have OpenCL.

Tom

---

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

Tom I was just looking at your 2700 Win 10 host with the 1060 3GB card. https://setiathome.berkeley.edu/show_host_detail.php?hostid=8671092

and I saw a SoG command line I had never come across before. I see you have defined 6 kernels instead of the standard 2 and that seems to really speed up the crunching. I wonder why that isn't in more use? Simply lack of exposure or commonality?

That is a great question. I dismounted that HD and installed another one to run LInux/Cuda91. I will need to re-mount that HD to see exactly what I did. As for why I am not sure. I usually follow the advice I have been given by people like you or Wiggo.

Let me see now...

Tom

The app_config.xml I was using is 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>2.0</cpu_usage>
</gpu_versions>
</app>
</app_config>


<project_max_concurrent>36</project_max_concurrent>

The MB command line was this:

-sbs 1024 -period_iterations_num 10 -spike_fft_thresh 4096 -tune 1 64 1 4 -tune 2 64 1 4 -tune 3 64 1 4 -tune 4 64 1 4 -tune 5 64 1 4 -tune 6 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 

Now the question of why I put in all those "-tune 1...." is that I THINK the -tune 1, -tune 2 referenced different video cards. Card 1, Card 2, etc. Now the reason I set that up is because I was, once again, trying to get 3 or 4 gpus to run on "that box".

I remain clueless, otherwise. Heck, I didn't even realize I was getting a 50% improvement.
-edit-
I went and looked at the SOG tasks for the gtx 1060 3G. And while there are some really low time numbers, there are also some 10 minute tasks. I remember running pretty reliably in the 7-8 minute range years ago.

I have another box that I could drop a gtx 1060 3GB into. And play with the command line after I establish a baseline.
---edit---

The AP command line file appears to be empty.

Tom

Ok, I have a Windows/Nvidia box (gtx 1060 3GB) that is showing stable run times on the SOG task off around 7 minutes. https://setiathome.berkeley.edu/show_host_detail.php?hostid=8281049

I am going to copy the above command line in there and "see what happens".
Here is the command line I replaced:

-sbs 192 -period_iterations_num 10 -spike_fft_thresh 4048  -oclfft_tune_gr 256 -oclfft_tune_lr 16 -oclfft_tune_wg 256 -oclfft_tune_ls 512 -oclfft_tune_bn 64 -oclfft_tune_cw 64 -tt 1500 -tune 1 64 1 4

Tom

---

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