Stock beta has been running for a couple of weeks on some of my machines, stable now. I run opti apps in main Seti and am fairly used to app_info. I thought I would try the new opti (365) here on Beta but I am unsure of the app_info. Could anyone post an app_info for running MB on cpu and gpu.

I am running Nvida GTX520.

Thanks in advance,

Dave

Here is my appinfo.

Beware i´m running 64 bit OS so you need to change platform entry and plan class for your GPU as well.

<app_info>
<app>
<name>setiathome_v7</name>
<user_friendly_name>SETI@home v7 BETA</user_friendly_name>
</app>
<file_info>
<name>MB7_win_x86_SSE2_CPU_r365.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>694</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>MB7_win_x86_SSE2_CPU_r365.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_name>setiathome_v7</app_name>
<version_num>694</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>MB7_win_x86_SSE2_CPU_r365.exe</file_name>
<main_program/>
</file_ref>
</app_version>

<app>
<name>setiathome_v7</name>
<user_friendly_name>SETI@home v7</user_friendly_name>
</app>

<file_info>
<name>MB7_win_x86_SSE3_OpenCL_ATi_HD5_r365.exe</name>
<executable/>
</file_info>
<file_info>
<name>MultiBeam_Kernels_r365.cl</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>691</version_num>
<file_ref>

<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>691</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>0.05</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline>-period_iterations_num 15 -instances_per_device 2</cmdline>
<file_ref>
<file_name>MB7_win_x86_SSE3_OpenCL_ATi_HD5_r365.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r365.cl</file_name>
<copy_file/>
</file_ref>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
</app_version>

</app_info>

---

With each crime and every kindness we birth our future.

Mike,

Thank you. Is there documentation somewhere that describes the acceptable entries. I am not sure what to change them to.

Dave

[quote]
Here is my appinfo.

Beware i´m running 64 bit OS so you need to change platform entry and plan class for your GPU as well.

<app_info>
<app>
<name>setiathome_v7</name>
<user_friendly_name>SETI@home v7 BETA</user_friendly_name>
</app>
<file_info>
<name>MB7_win_x86_SSE2_CPU_r365.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>694</version_num>
<platform>windows_intelx86</platform>
-----[snipped]-----

Mike, why do you run the SSE2 version for CPU, SSE3 or SSSE3 is faster!
(Perhaps the CPU says otherwise, f.i. SSE2)
Couldn't help noticing...

Anotherthing, all apps are 32bit, although more and more systems run64bit OSses.
LINUX flavors and with the arrival of Windows (2000), XP, VISTA and 7, 64bit has become more and more mainstream.
Probably, cause a good part of the older hosts, will likeley run a 32bit version of * NUX of Windows.
(The SET and forget, crowd)

Mike, why do you run the SSE2 version for CPU, SSE3 or SSSE3 is faster!
(Perhaps the CPU says otherwise, f.i. SSE2)
Couldn't help noticing...

Because his AMD Phenom(tm) II X6 1090T Processor Doesn't have SSSE3?

Claggy

Mike was kind enough to supply me with his app_info. Anyone know how I should change it to run with this computer:

http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=53052

Mike, why do you run the SSE2 version for CPU, SSE3 or SSSE3 is faster!
(Perhaps the CPU says otherwise, f.i. SSE2)
Couldn't help noticing...

Because his AMD Phenom(tm) II X6 1090T Processor Doesn't have SSSE3?

Claggy

But maybe SSE3, I can't think of CPUs, without this feature, exept ofcause older
types, such as the first Athlons.
(I had 2 of them, SSE2 not SSE3 and not that fast).

Mike was kind enough to supply me with his app_info. Anyone know how I should change it to run with this computer:

http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=53052

All Pentium D cpus support SSE3.

---

_\|/_
U r s

<app_info>
	<app>
		<name>setiathome_v7</name>
		<user_friendly_name>SETI@home v7 BETA</user_friendly_name>
	</app>
	<file_info>
		<name>MB7_win_x86_SSSE3x_CPU_r365.exe</name>
		<executable/>
	</file_info>
	<app_version>
		<app_name>setiathome_v7</app_name>
		<version_num>694</version_num>
		<platform>windows_intelx86</platform>
		<file_ref>
			<file_name>MB7_win_x86_SSSE3x_CPU_r365.exe</file_name>
			<main_program/>
		</file_ref>
	</app_version>
	<app_version>
		<app_name>setiathome_v7</app_name>
		<version_num>694</version_num>
		<platform>windows_x86_64</platform>
		<file_ref>
			<file_name>MB7_win_x86_SSSE3x_CPU_r365.exe</file_name>
			<main_program/>
		</file_ref>
	</app_version>
	<app>
		<name>setiathome_v7</name>
		<user_friendly_name>SETI@home v7</user_friendly_name>
	</app>
	<file_info>
		<name>MB7_win_x86_SSE3_OpenCL_NV_r365.exe</name>
		<executable/>
	</file_info>
	<file_info>
		<name>MultiBeam_Kernels_r365.cl</name>
		<executable/>
	</file_info>
	<app_version>
		<app_name>setiathome_v7</app_name>
		<version_num>691</version_num>
		<flops>120000000000</flops>
		<platform>windows_intelx86</platform>
		<avg_ncpus>0.05</avg_ncpus>
		<max_ncpus>0.05</max_ncpus>
		<plan_class>cuda_fermi</plan_class>
		<cmdline>-period_iterations_num 10 -instances_per_device 2</cmdline>
		<file_ref>
			<file_name>MB7_win_x86_SSE3_OpenCL_NV_r365.exe</file_name>
			<main_program/>
		</file_ref>
		<file_ref>
			<file_name>MultiBeam_Kernels_r365.cl</file_name>
			<copy_file/>
		</file_ref>
		<coproc>
			<type>CUDA</type>
			<count>0.5</count>
		</coproc>
	</app_version>
</app_info>

I personally don't use the CPU (only GPU), but this app_info should work for your rig. If you experience gui-lags of driver-resets, you should enlarge the value of -period_iterations_num to something higher like 15.
If things run well you can try 3 WU's : -instances_per_device 3 and <count>0.33</count>

TeeVeeEss wrote:

...
I personally don't use the CPU (only GPU), but this app_info should work for your rig. If you experience gui-lags of driver-resets, you should enlarge the value of -period_iterations_num to something higher like 15.
If things run well you can try 3 WU's : -instances_per_device 3 and <count>0.33</count>

That looks almost right, but a Pentium D does not have SSSE3 so change all the "MB7_win_x86_SSSE3x_CPU_r365.exe" to "MB7_win_x86_SSE2_CPU_r365.exe".

With 2GB the card will run more than one instance as suggested, but as it's the least capable of the 5xx series it might peak at 2 rather than 3 or higher. Definitely worth trying to see what it likes best.

If it works well with multiple tasks, perhaps setting the <avg_ncpus>0.05</avg_ncpus> and <max_ncpus>0.05</max_ncpus> higher so that when the GPU is actually doing multiple tasks BOINC will run one less CPU task. A setting of 0.51 would give that effect when there are 2 or more tasks on GPU, 0.34 when there are 3 or more.

                                                                 Joe

Mike, why do you run the SSE2 version for CPU, SSE3 or SSSE3 is faster!
(Perhaps the CPU says otherwise, f.i. SSE2)
Couldn't help noticing...

Because his AMD Phenom(tm) II X6 1090T Processor Doesn't have SSSE3?

Claggy

Yes, i would of course if supported.

---

With each crime and every kindness we birth our future.

TeeVeeEss wrote:

...
I personally don't use the CPU (only GPU), but this app_info should work for your rig. If you experience gui-lags of driver-resets, you should enlarge the value of -period_iterations_num to something higher like 15.
If things run well you can try 3 WU's : -instances_per_device 3 and <count>0.33</count>

That looks almost right, but a Pentium D does not have SSSE3 so change all the "MB7_win_x86_SSSE3x_CPU_r365.exe" to "MB7_win_x86_SSE2_CPU_r365.exe".

With 2GB the card will run more than one instance as suggested, but as it's the least capable of the 5xx series it might peak at 2 rather than 3 or higher. Definitely worth trying to see what it likes best.

If it works well with multiple tasks, perhaps setting the <avg_ncpus>0.05</avg_ncpus> and <max_ncpus>0.05</max_ncpus> higher so that when the GPU is actually doing multiple tasks BOINC will run one less CPU task. A setting of 0.51 would give that effect when there are 2 or more tasks on GPU, 0.34 when there are 3 or more.

                                                                 Joe

Still platform info needs to be changed.

<platform>windows_x86_64</platform>

to

<platform>windows_intelx86</platform>

This should work Dave.

<app_info>
<app>
<name>setiathome_v7</name>
<user_friendly_name>SETI@home v7 BETA</user_friendly_name>
</app>
<file_info>
<name>MB7_win_x86_SSE2_CPU_r365.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>694</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>MB7_win_x86_SSE2_CPU_r365.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>694</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>MB7_win_x86_SSE2_CPU_r365.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_v7</name>
<user_friendly_name>SETI@home v7</user_friendly_name>
</app>
<file_info>
<name>MB7_win_x86_SSE3_OpenCL_NV_r365.exe</name>
<executable/>
</file_info>
<file_info>
<name>MultiBeam_Kernels_r365.cl</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>691</version_num>
<flops>120000000000</flops>
<platform>windows_intelx86</platform>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>0.05</max_ncpus>
<plan_class>cuda_fermi</plan_class>
<cmdline>-period_iterations_num 15 -instances_per_device 2</cmdline>
<file_ref>
<file_name>MB7_win_x86_SSE3_OpenCL_NV_r365.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r365.cl</file_name>
<copy_file/>
</file_ref>
<coproc>
<type>CUDA</type>
<count>0.5</count>
</coproc>
</app_version>
</app_info>

---

With each crime and every kindness we birth our future.

Mike wrote:

Still platform info needs to be changed.

But it's already in the app_info:

(snip...)
<app_name>setiathome_v7</app_name>
<version_num>694</version_num>
<platform>windows_intelx86</platform> (your modification)
<file_ref>
<file_name>MB7_win_x86_SSE2_CPU_r365.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>694</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>MB7_win_x86_SSE2_CPU_r365.exe</file_name>
<main_program/>
</file_ref>
</app_version>
(snip...)

Yes, because i did it.

---

With each crime and every kindness we birth our future.

Yes, because i did it.

Before your change, both platforms were there for the CPU application. That would have worked just fine, as will your revision which probably has two identical <app_version> sections for the CPU app. The cleanest revision would have only what's actually needed, but redundant information is not harmful.

                                                                 Joe