Lunatics beta6 and using 2 different gpus?

Message boards : Number crunching : Lunatics beta6 and using 2 different gpus?
Message board moderation

To post messages, you must log in.

1 · 2 · 3 · Next

AuthorMessage
Profile Tom M
Volunteer tester

Send message
Joined: 28 Nov 02
Posts: 5124
Credit: 276,046,078
RAC: 462
Message 1873646 - Posted: 17 Jun 2017, 20:11:08 UTC

Hi,
I am using the beta6 distribution of Lunatics with a manual upgrade of the r3557 to r3584.

I have a "spare" GTX 750 Ti that will fit next to my GTX 1060. The 750 is a LP so it gives clearance to the 1060 card.

Windows7 and Gpu-Z both recognize the card.

I have worked out what is supposed to be a "Multibeam_NV_config.xml" that will allow 2 asymmetrical gpus to share work efficiently under Seti. That file is in the Seti dir. The 1060 is gpu 0 and the 750 is gpu 1.

<device0>
<period_iterations_num>4</period_iterations_num>
<spike_fft_thresh>4096</spike_fft_thresh>
<sbs>1024</sbs>
</device0>
<device1>
<period_iterations_num>4</period_iterations_num>
<spike_fft_thresh>2048</spike_fft_thresh>
<sbs>512</sbs>
</device1>

I understand that the cc_config.xml has to have "use_all_gpus" in it. In the Boinc dir.

Mine looks like:

<cc_config>
<options>
<use_all_gpus>1</use_all_gpus>
</options>
</cc_config>

As of the moment, Boinc/Seti is only running the 1060.

What simple mistake am I overlooking?

Thanks.

Tom
A proud member of the OFA (Old Farts Association).
ID: 1873646 · Report as offensive
Profile Mike Special Project $75 donor
Volunteer tester
Avatar

Send message
Joined: 17 Feb 01
Posts: 34253
Credit: 79,922,639
RAC: 80
Germany
Message 1873654 - Posted: 17 Jun 2017, 20:30:32 UTC

The Multibeam_NV_config.xml needs to be defined in appinfo.xml as well to work properly.


With each crime and every kindness we birth our future.
ID: 1873654 · Report as offensive
Profile Tom M
Volunteer tester

Send message
Joined: 28 Nov 02
Posts: 5124
Credit: 276,046,078
RAC: 462
Message 1873692 - Posted: 17 Jun 2017, 23:12:05 UTC - in response to Message 1873654.  

The Multibeam_NV_config.xml needs to be defined in appinfo.xml as well to work properly.


Thank you. Can you point me to more details? Or should I post my current appinfo.xml?

Tom
A proud member of the OFA (Old Farts Association).
ID: 1873692 · Report as offensive
Profile Mike Special Project $75 donor
Volunteer tester
Avatar

Send message
Joined: 17 Feb 01
Posts: 34253
Credit: 79,922,639
RAC: 80
Germany
Message 1873763 - Posted: 18 Jun 2017, 7:25:05 UTC
Last modified: 18 Jun 2017, 7:27:07 UTC

Something like that.

<app>
<name>setiathome_v8</name>
</app>
<file_info>
<name>MBv8_8.22r3584_sse2_clAMD_HD5_SoG_x86_64-pc-linux-gnu</name>
<executable/>
</file_info>
<file_info>
<name>MultiBeam_Kernels_r3584.cl</name>
</file_info>
<file_info>
<name>mb_cmdline.txt</name>
</file_info>
<file_info>
<name>Multibeam_ATI_config.xml</name>
</file_info>

<app_version>
<app_name>setiathome_v8</app_name>
<version_num>803</version_num>
<platform>windows_intelx86</platform>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>0.05</max_ncpus>
<plan_class>opencl_ati_sah</plan_class>
<cmdline>-device 0 -period_iterations_num 40 -instances_per_device 3</cmdline>
<flops></flops>
<file_ref>
<file_name>MBv8_8.22r3584_sse2_clAMD_HD5_SoG_x86_64-pc-linux-gnu</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r3584.cl</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline.txt</file_name>
</file_ref>
<file_ref>
<file_name>Multibeam_ATI_config.xml</file_name>
</file_ref>

</app_version>

Watch out for any typos.
I lost my cache a few times before i got it working.


With each crime and every kindness we birth our future.
ID: 1873763 · Report as offensive
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13161
Credit: 1,160,866,277
RAC: 1,873
United States
Message 1873766 - Posted: 18 Jun 2017, 7:37:06 UTC - in response to Message 1873763.  

Good information here. I was wondering how I was going to implement different SoG tuning parameters if/when I get a GTX 970 added into the Ryzen system with two 1070s already in it.

I always open the app_info.xml with Chrome after editing it. Chrome will check for simple syntax errors like missing a closing ident. It won't show up simple typos or misnamings though.
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 1873766 · Report as offensive
Stephen "Heretic" Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 20 Sep 12
Posts: 5557
Credit: 192,787,363
RAC: 628
Australia
Message 1873769 - Posted: 18 Jun 2017, 7:53:12 UTC - in response to Message 1873766.  

Good information here. I was wondering how I was going to implement different SoG tuning parameters if/when I get a GTX 970 added into the Ryzen system with two 1070s already in it.

I always open the app_info.xml with Chrome after editing it. Chrome will check for simple syntax errors like missing a closing ident. It won't show up simple typos or misnamings though.


. . If you intend to add a card think GTX1060 3GB over a GTX970. It will give the same or better results and use way less power.

Stephen
ID: 1873769 · Report as offensive
Profile Mike Special Project $75 donor
Volunteer tester
Avatar

Send message
Joined: 17 Feb 01
Posts: 34253
Credit: 79,922,639
RAC: 80
Germany
Message 1873771 - Posted: 18 Jun 2017, 8:08:26 UTC - in response to Message 1873766.  

Good information here. I was wondering how I was going to implement different SoG tuning parameters if/when I get a GTX 970 added into the Ryzen system with two 1070s already in it.

I always open the app_info.xml with Chrome after editing it. Chrome will check for simple syntax errors like missing a closing ident. It won't show up simple typos or misnamings though.


I found that Boinc 7 is more picky than Boinc 6 with structures.
I had to move those lines a couple times to get it working back then.
Not sure it was the early versions of Boinc 7.


With each crime and every kindness we birth our future.
ID: 1873771 · Report as offensive
Profile Tom M
Volunteer tester

Send message
Joined: 28 Nov 02
Posts: 5124
Credit: 276,046,078
RAC: 462
Message 1873785 - Posted: 18 Jun 2017, 11:50:39 UTC - in response to Message 1873766.  

Good information here. I was wondering how I was going to implement different SoG tuning parameters if/when I get a GTX 970 added into the Ryzen system with two 1070s already in it.

I always open the app_info.xml with Chrome after editing it. Chrome will check for simple syntax errors like missing a closing ident. It won't show up simple typos or misnamings though.


Keith,
The file that you can use for customization of each GPU is called "Multibeam_NV_config.xml It is documented in the MB*sog_Readme.txt If you are running stock seti you simply copy it into the seti data directory. If you are running the Lunatics distribution you need to hand edit the file that Mike just posted to add that file name in a bunch of different locations in that file.

The "NV" is specific to each kind of Gpu. And is documented. So if you were running both an NV card and an ATI card you would have two versions of that file.

HTH,
Tom
A proud member of the OFA (Old Farts Association).
ID: 1873785 · Report as offensive
Profile Tom M
Volunteer tester

Send message
Joined: 28 Nov 02
Posts: 5124
Credit: 276,046,078
RAC: 462
Message 1873786 - Posted: 18 Jun 2017, 11:53:44 UTC - in response to Message 1873763.  

Thank you Mike. I have been studying the appinfo.xml file and what you are showing makes sense. So I will spend some time with a copy of the file in another directory as well as your file open so I can see if I can insert the "multibeam_NV_config.xml" in the correct locations.

Tom
A proud member of the OFA (Old Farts Association).
ID: 1873786 · Report as offensive
Profile Mike Special Project $75 donor
Volunteer tester
Avatar

Send message
Joined: 17 Feb 01
Posts: 34253
Credit: 79,922,639
RAC: 80
Germany
Message 1873829 - Posted: 18 Jun 2017, 14:11:38 UTC
Last modified: 18 Jun 2017, 14:13:40 UTC

I have tested it live during alpha tests years ago when device specific xml was implemented.
I don`t suggest anything i haven`t tested myself.


With each crime and every kindness we birth our future.
ID: 1873829 · Report as offensive
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13161
Credit: 1,160,866,277
RAC: 1,873
United States
Message 1873849 - Posted: 18 Jun 2017, 15:42:35 UTC - in response to Message 1873769.  

Well I was going to use it simply because I have four old ones on the shelf doing nothing. I will have to play games with PCIe extenders though. The GTX 1060 short cards would be the simpler installation, just would have to buy into the extra cost. I have been waffling over this decision for quite a while. I guess I had better go review Shaggie's tables again.
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 1873849 · Report as offensive
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13161
Credit: 1,160,866,277
RAC: 1,873
United States
Message 1873850 - Posted: 18 Jun 2017, 15:48:51 UTC - in response to Message 1873785.  


Keith,
The file that you can use for customization of each GPU is called "Multibeam_NV_config.xml It is documented in the MB*sog_Readme.txt If you are running stock seti you simply copy it into the seti data directory. If you are running the Lunatics distribution you need to hand edit the file that Mike just posted to add that file name in a bunch of different locations in that file.

The "NV" is specific to each kind of Gpu. And is documented. So if you were running both an NV card and an ATI card you would have two versions of that file.

HTH,
Tom

Thanks for pointing out where the documentation is. I had assumed after reading the client_state and app_config docs in the BOINC repository that the changes needed would have to go into app_config since that is where [device] tags are located. I see that I was wrong.
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 1873850 · Report as offensive
Profile Tom M
Volunteer tester

Send message
Joined: 28 Nov 02
Posts: 5124
Credit: 276,046,078
RAC: 462
Message 1873911 - Posted: 18 Jun 2017, 23:46:06 UTC - in response to Message 1873763.  

Something like that.

------

Watch out for any typos.
I lost my cache a few times before i got it working.


Mike, I ran this modified version through the Chrome web browser to try to catch any syntax errors. I am chopping off the section of Astropulse on the assumption its not relevant. I am trying to avoid ignorant errors. Please let me know when you see any. :)

<app_info> 
       <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>
<file_info>
 <name>Multibeam_NV_config.xml</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>1</count>
        </coproc>
        <file_ref>
            <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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>1</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>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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>1</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>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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_sah</plan_class>
        	<cmdline></cmdline>	
	<coproc>
            <type>CUDA</type>
            <count>1</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>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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>
        <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>1</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>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <plan_class>opencl_nvidia_sah</plan_class>
        	<cmdline></cmdline>	
	<coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </file_name>
            <open_name>mb_cmdline.txt</open_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_v8</app_name>
        <version_num>819</version_num>
        <platform>windows_x86_64</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>1</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>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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_x86_64</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>1</count>
        </coproc>
        <file_ref>
            <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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_x86_64</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>1</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>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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_x86_64</platform>
        <api_version>7.5.0</api_version>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <plan_class>opencl_nvidia_sah</plan_class>
        	<cmdline></cmdline>	
	<coproc>
            <type>CUDA</type>
            <count>1</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><file_name>
 <name>Multibeam_NV_config.xml</name>
 </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_x86_64</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>1</count>
        </coproc>
        <file_ref>
            <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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_x86_64</platform>
        <api_version>7.5.0</api_version>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <plan_class>opencl_nvidia_sah</plan_class>
        	<cmdline></cmdline>	
	<coproc>
            <type>CUDA</type>
            <count>1</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>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <plan_class>cuda50</plan_class>
        	<cmdline></cmdline>	
	<coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <plan_class>cuda42</plan_class>
        	<cmdline></cmdline>	
	<coproc>
            <type>CUDA</type>
            <count>1</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>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <plan_class>cuda32</plan_class>
        	<cmdline></cmdline>	
	<coproc>
            <type>CUDA</type>
            <count>1</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>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <plan_class>cuda23</plan_class>
        	<cmdline></cmdline>	
	<coproc>
            <type>CUDA</type>
            <count>1</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>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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_x86_64</platform>
        <api_version>7.5.0</api_version>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <plan_class>cuda50</plan_class>
        	<cmdline></cmdline>	
	<coproc>
            <type>CUDA</type>
            <count>1</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>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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_x86_64</platform>
        <api_version>7.5.0</api_version>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <plan_class>cuda42</plan_class>
        	<cmdline></cmdline>	
	<coproc>
            <type>CUDA</type>
            <count>1</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>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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_x86_64</platform>
        <api_version>7.5.0</api_version>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <plan_class>cuda32</plan_class>
        	<cmdline></cmdline>	
	<coproc>
            <type>CUDA</type>
            <count>1</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>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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_x86_64</platform>
        <api_version>7.5.0</api_version>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <plan_class>cuda23</plan_class>
        	<cmdline></cmdline>	
	<coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </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>
<file_name>
 <name>Multibeam_NV_config.xml</name>
 </file_name>
            <open_name>mb_cmdline.txt</open_name>
        </file_ref>
    </app_version>
</app_info> 

A proud member of the OFA (Old Farts Association).
ID: 1873911 · Report as offensive
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13161
Credit: 1,160,866,277
RAC: 1,873
United States
Message 1873912 - Posted: 19 Jun 2017, 0:03:13 UTC

I don 't see anything wrong with it. Whether it obeys your definitions in Multibeam_NV_config.xml is another story. And as long as the file name matches EXACTLY what the xml filename is... it shouldn't dump work as far as I can tell.
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 1873912 · Report as offensive
Profile Tom M
Volunteer tester

Send message
Joined: 28 Nov 02
Posts: 5124
Credit: 276,046,078
RAC: 462
Message 1873956 - Posted: 19 Jun 2017, 7:56:54 UTC - in response to Message 1873912.  

I don 't see anything wrong with it. Whether it obeys your definitions in Multibeam_NV_config.xml is another story. And as long as the file name matches EXACTLY what the xml filename is... it shouldn't dump work as far as I can tell.


Mike,
Well, I tried it and after a while the mb*sog.txt file disappeared and so did the Multibeam_NV_config.xml file. Since I had a copy of the original app_info.xml and reloaded that, re-created/loaded the mb*sog.txt file and pulled the gtx 750 ti.

I pulled the gtx 750 ti after I tried putting the Multibeam_NV_config.xml file in my SetiBeta directory and deleting the equivalent entries from the mb*sog.txt and the Gpu-Z gave no indication that the Multibeam_NV_config.xml was being read (eg. no memory used changes). I was/am running SetiBeta stock SOG tasks at the time.

I am now convinced that I don't know what I am doing :) Or Boinc is behaving strangely. And that the GFlops number has gone down since I added the gtx 750 ti. So its back to one gpu.

If someone has another idea I would be willing to reinstall the 750 ti and try it. But I am out of ideas.

Thank you for your time and effort, Mike.

Tom
A proud member of the OFA (Old Farts Association).
ID: 1873956 · Report as offensive
Grant (SSSF)
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 13720
Credit: 208,696,464
RAC: 304
Australia
Message 1873957 - Posted: 19 Jun 2017, 8:04:28 UTC - in response to Message 1873956.  
Last modified: 19 Jun 2017, 8:05:17 UTC

And that the GFlops number has gone down since I added the gtx 750 ti. So its back to one gpu.
If someone has another idea I would be willing to reinstall the 750 ti and try it. But I am out of ideas.

Are you comparing the same type of WUs?
Shorty, mid range & longer running Areibo WUs will all produce steadily decreasing APR numbers. GBT work will produce lower numbers again. Longer running GBT work even lower still.

And even with different values for the different cards, crunching the same type of work as before the GTX 750Ti will process slower than the other card, bringing down the APR which is based on all cards on the system.
What you have to compare are run times for each card, for a given WU, against itself, for a given setting.
Grant
Darwin NT
ID: 1873957 · Report as offensive
Profile Brent Norman Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester

Send message
Joined: 1 Dec 99
Posts: 2786
Credit: 685,657,289
RAC: 835
Canada
Message 1873962 - Posted: 19 Jun 2017, 8:19:57 UTC - in response to Message 1873956.  

If it is deleting your TXT and XML file, it is because they are not properly defined. That is likely due to the bloated app_info file.

There are many, many sections of that file that are not needed, they are there only for compatibility when installing Lunatics to preserve existing cache. You only need FOUR sections, MB CPU, MB GPU, AP CPU, AP GPU - that's it.

Look at what version of SoG you are running. Likely it is 8.20, so you can delete sections 8.12, 8.19, etc for SOG. The same goes for each application. You will end up with a workable file that is not 32 pages long.

The deletions are probably occurring because the same files are not defined in each and every SoG section.

At least clean up the SoG section, it is easy. Just make sure you get the entire block, and only that block to delete. Add some carriage returns between sections for readability while your at it :)
ID: 1873962 · Report as offensive
rob smith Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer moderator
Volunteer tester

Send message
Joined: 7 Mar 03
Posts: 22158
Credit: 416,307,556
RAC: 380
United Kingdom
Message 1873965 - Posted: 19 Jun 2017, 8:47:43 UTC

Mike, I ran this modified version through the Chrome web browser to try to catch any syntax errors. I am chopping off the section of Astropulse on the assumption its not relevant. I am trying to avoid ignorant errors.


Running through with Chrome is not a good idea - while the file extension is ".XML" the content is not "pure" XML, but a strange hybrid that just looks like XML. You would be far better using a decent text editor, or even Notepad which do not try to correct errors that aren't errors.
Before you started fiddling did you actually try Mike's example? If it is like any other example he's posted here, or in a PM, he will have tested it first and made sure it works.
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?
ID: 1873965 · Report as offensive
Profile Tom M
Volunteer tester

Send message
Joined: 28 Nov 02
Posts: 5124
Credit: 276,046,078
RAC: 462
Message 1873972 - Posted: 19 Jun 2017, 9:46:05 UTC - in response to Message 1873962.  

If it is deleting your TXT and XML file, it is because they are not properly defined. That is likely due to the bloated app_info file.


Looks like I need to study the app_info.xml file some more and then try some serious editing.

Thank you for the guidance.

Tom
A proud member of the OFA (Old Farts Association).
ID: 1873972 · Report as offensive
Profile Tom M
Volunteer tester

Send message
Joined: 28 Nov 02
Posts: 5124
Credit: 276,046,078
RAC: 462
Message 1873973 - Posted: 19 Jun 2017, 9:56:05 UTC - in response to Message 1873965.  

Before you started fiddling did you actually try Mike's example?


Bob,
Mike posted a Linux example of the app_info.xml file. Since I am running windows, I couldn't "try" his example. I ran the xml file "thru" chrome to see if it would show up any "syntax errors" (it didn't). I don't use Chrome for editing. I have been using notepad.

I am trying something out since I have a "spare" Gtx 750 ti that will fit within the power supply limits of the box I currently have a Gtx 1060 installed on. No, it will not run 2 1060's, its got a 435 watt ps. Good for one, but apparently not good for two.

As Mike pointed out in another post I have two issues. 1) I need a radically cleaned up and edited app_info.xml file so I can more easily debug and maintain it. (So it will stop eating a couple of files) 2) I need to make sure I am comparing apples to apples between the two boxes both running Gtx 1060's but one running the Stock seti SOG and the other some version of the Lunatics SOG. The apples are the mix of data that I am analyzing.

So it is a complicated project. Just what I need to keep me distracted from the rest of my complicated life. :)

Tom
A proud member of the OFA (Old Farts Association).
ID: 1873973 · Report as offensive
1 · 2 · 3 · Next

Message boards : Number crunching : Lunatics beta6 and using 2 different gpus?


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.