Posts by Kashra

1) (Message 8754)
Posted 18 Jan 2025 by Kashra
Post:
I was able to locate the problem. It was the app_info file.

It was:

		<coproc>
		<type>AMD</type>
		<count>0.5</count>
		</coproc>


But "AMD" is not known, and "ATI" has to be used, otherwise the card is missing.


<coproc>
		<type>ATI</type>
		<count>1</count>
		</coproc>
	</app_version>





For someone who wants to run specific apps, here is the working app_info.xml file which works with AMD/ATI cards.


<app_info>
    <app>
        <name>period_search</name>
        <user_friendly_name>Period Search Application</user_friendly_name>
    </app>
    <file_info>
        <name>period_search_10213_windows_x86_64__fma_win10.exe</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>period_search</app_name>
        <version_num>10215</version_num>
        <api_version>7.14.0</api_version>
        <plan_class>fma_win10</plan_class>
        <avg_ncpus>1.000000</avg_ncpus>
        <file_ref>
            <file_name>period_search_10213_windows_x86_64__fma_win10.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>



    <app>
        <name>period_search</name>
        <user_friendly_name>Period Search Application</user_friendly_name>
    </app>
    <file_info>
        <name>period_search_10215_windows_x86_64__avx512_win10.exe</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>period_search</app_name>
        <version_num>10215</version_num>
        <api_version>7.14.0</api_version>
        <plan_class>avx512_win10</plan_class>
        <avg_ncpus>1.000000</avg_ncpus>
        <file_ref>
            <file_name>period_search_10215_windows_x86_64__avx512_win10.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>
	


    <app>
        <name>period_search</name>
        <user_friendly_name>Period Search Application</user_friendly_name>
    </app>
    <file_info>
        <name>period_search_10214_windows_x86_64__sse2_win10.exe</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>period_search</app_name>
        <version_num>10214</version_num>
        <api_version>7.14.0</api_version>
        <plan_class>sse2_win10</plan_class>
        <avg_ncpus>1.000000</avg_ncpus>
        <file_ref>
            <file_name>period_search_10214_windows_x86_64__sse2_win10.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>


	<app>
		<name>period_search</name>
		<user_friendly_name>Asteroids</user_friendly_name>
	</app>

	<file_info>
		<name>period_search_10220_windows_x86_64__opencl_102_amd_win.exe</name>
		<executable/>	
	</file_info>
	
	<app_version>
		<app_name>period_search</app_name>
		<version_num>10220</version_num>
		<avg_ncpus>1.00</avg_ncpus>
		<max_ncpus>1.00</max_ncpus>
		<plan_class>opencl_102_amd_win</plan_class>
		<file_ref>
			<file_name>period_search_10220_windows_x86_64__opencl_102_amd_win.exe</file_name>
			<main_program/>
		</file_ref>
		<coproc>
		<type>ATI</type>
		<count>0.5</count>
		</coproc>
	</app_version>
	

	
</app_info>
2) (Message 8752)
Posted 18 Jan 2025 by Kashra
Post:
Hi there,

I usually use my app_info.xml file to select AVX512 workunits among some other well performing CPU extensions.

The only thing I did not manage to get to work so far is AMD GPU related work units.
If I add the GPU related stuff to the app_ifo file, no GPU workunits are downloaded anymore.

Here is my app_info file, does anyone spot mistakes in the last part, which is the GPU part?
<app_info>
    <app>
        <name>period_search</name>
        <user_friendly_name>Period Search Application</user_friendly_name>
    </app>
    <file_info>
        <name>period_search_10213_windows_x86_64__fma_win10.exe</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>period_search</app_name>
        <version_num>10213</version_num>
        <api_version>7.14.0</api_version>
        <plan_class>fma_win10</plan_class>
        <avg_ncpus>1.000000</avg_ncpus>
        <file_ref>
            <file_name>period_search_10213_windows_x86_64__fma_win10.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>



    <app>
        <name>period_search</name>
        <user_friendly_name>Period Search Application</user_friendly_name>
    </app>
    <file_info>
        <name>period_search_10215_windows_x86_64__avx512_win10.exe</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>period_search</app_name>
        <version_num>10213</version_num>
        <api_version>7.14.0</api_version>
        <plan_class>avx512_win10</plan_class>
        <avg_ncpus>1.000000</avg_ncpus>
        <file_ref>
            <file_name>period_search_10215_windows_x86_64__avx512_win10.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>
	



    <app>
        <name>period_search</name>
        <user_friendly_name>Period Search Application</user_friendly_name>
    </app>
    <file_info>
        <name>period_search_10214_windows_x86_64__sse2_win10.exe</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>period_search</app_name>
        <version_num>10214</version_num>
        <api_version>7.14.0</api_version>
        <plan_class>sse2_win10</plan_class>
        <avg_ncpus>1.000000</avg_ncpus>
        <file_ref>
            <file_name>period_search_10214_windows_x86_64__sse2_win10.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>



	<app>
		<name>period_search</name>
		<user_friendly_name>Asteroids</user_friendly_name>
	</app>

	<file_info>
		<name>period_search_10220_windows_x86_64__opencl_102_amd_win.exe</name>
		<executable/>	
	</file_info>
	
	<app_version>
		<app_name>period_search</app_name>
		<version_num>10220</version_num>
		<avg_ncpus>1.00</avg_ncpus>
		<max_ncpus>1.00</max_ncpus>
		<plan_class>opencl_102_amd_win</plan_class>
		<file_ref>
			<file_name>period_search_10220_windows_x86_64__opencl_102_amd_win.exe</file_name>
			<main_program/>
		</file_ref>
		<coproc>
		<type>AMD</type>
		<count>1</count>
		</coproc>
	</app_version>
	
	
	
	
	
	
	
	
	
	
	
	
</app_info>
3) (Message 8150)
Posted 26 Nov 2023 by Kashra
Post:
Is there a way of testing the performance of SSE / AVX / FMA etc. on an individual system?
Once there was a benchmark package available, but I could not find it anymore and it was outdated (more than 10 years) too.

Does anyone know a way how to test for the best instruction set apart from letting boinc choose based on results after some time.

Because I noticed other important metrics too, like system responsiveness or power consumption vs. speed or in other words efficiency.
4) (Message 8092)
Posted 3 Oct 2023 by Kashra
Post:
Hi,

I would like to only receive AVX/FMA workunits, if possible. I am new to the project and noticed that the AVX units are way faster (about half in time compared to SSE ones) if only AVX are active. I assume that my Xeon CPUs "prefer" these instruction sets in terms of efficiency over the SSE ones. After all AVX is there to be an improvement over SSE instructions.

So my question is: Is there a way to only receive AVX/FMA workunits? I tried app_config.xml, but found that all applications are named the same, so I am not able to use app_config to do that.

Is there a way?