With the last WUs I never got any avx app, only SSE2/3. I have 7.2.16 that should support this feature. Is there a problem with the scheduler?

I'm not sure if I can help but...

There are a couple of possibilities concerning the avx feature. I know in Boinc version 7.0.64 when I use PrimeGrid, Windows does not report avx as a feature of the processor, even though I am running Windows 8 (when I initially start up Boinc it lists all the processor features in the log). My understanding is that Linux does not have this problem, even with Boinc 7.0.65 installed. So for PrimeGrid they devised a way to force the scheduler to give avx workunits to Windows computers. I'm not sure if that bug still applies to Boinc 7.2.16 or not. Also, Windows 7 supports avx if service pack 1 is installed. I believe it is enabled by default, but I could be wrong. I'm eager to try out the avx version of asteroid as well since the sse3 version is much faster than the stock app.

Avx version is faster on intel haswell only. Detection is problem.. we are discussing it now.

I have built an app_info file for those who want only crunch on avx on windows 64bit until a solution is found by admins. Before you use it download "period_search_10210_windows_x86_64__avx.exe" file.

<app_info>
<app>
    <name>period_search</name>
    <user_friendly_name>Period Search Application</user_friendly_name>
</app>
	<file_info>
		<name>period_search_10210_windows_x86_64__avx.exe</name>
		<executable/>
	</file_info>
	<app_version>
		<app_name>period_search</app_name>
		<version_num>1021</version_num>
  	    <avg_ncpus>1.00</avg_ncpus>
		<max_ncpus>1.00</max_ncpus> 
		<plan_class>avx</plan_class> 
		<file_ref>
			<file_name>period_search_10210_windows_x86_64__avx.exe</file_name>
			<main_program/>
		</file_ref>
	</app_version>
</app_info>

Lets see if its faster on an i5 than SSE3.

Edit:
Seems to be as fast as SSE3. Good luck if anyone has a Haswell CPU ;)

Haswell can crunch one task in abou 720s with avx version.

wow I definitely can't wait to try it out.

edit:

I know the admins at PrimeGrid@home allowed individual users to download the avx version by adjusting the PrimeGrid@home preferences page to allow users to force the server to download the avx program to the client computer with a checkbox so they could crunch with it, of course with the warning that you should not select the option unless your cpu has the avx function.

So it is only for Haswell, not SB or IB? Have you tested it? Assuming you have, I guess.

So it is only for Haswell, not SB or IB? Have you tested it? Assuming you have, I guess.

Sandy Bridge is not affected. The temps were still normal.

Temps were normal? Are you mixing French and English here? French "temps" translates to English "times" so I think you meant to say "the times were still normal".

@k3ack3r

It's possible to know the times would be normal even without testing. We know IB and SB don't have AVX therefore they cannot benefit from code designed to use AVX. At this time only Haswell CPUs have AVX therefore only Haswell CPUs will run the code faster.

We know IB and SB don't have AVX therefore they cannot benefit from code designed to use AVX.

"Upgraded features from Nehalem include:
Advanced Vector Extensions (AVX) 256-bit instruction set with wider vectors, new extensible syntax and rich functionality":
http://en.wikipedia.org/wiki/Sandy_Bridge

"Intel® AVX is a new-256 bit instruction set extension to Intel® SSE and is designed for applications that are Floating Point (FP) intensive.
It was released early 2011 as part of the Intel® microarchitecture code name Sandy Bridge processor family":
http://software.intel.com/en-us/intel-isa-extensions#pid-16007-1495

---

- ALF - "Find out what you don't do well ..... then don't do it!" :)

About the detection - scheduler works as it should. The problem is that the current version of BOINC manager doesn't detect avx on all processors that support it. Updated detection is already implemented in BOINC source codes (I don't know if it is already in branch) so when new version of BOINC manager is out it should detect avx on all processors (no related to version of os).

the download URL is

http://asteroidsathome.net/boinc/download/

---

terencewee*
Sicituradastra.

My friends, please beware AVX code on Hotwell = increased VID = more heat.
Mine is pulling 1.277V for 4.1GHz and temps shot up +10c (yeah, I'm lazy to optimize... :) ).

When your CPU gets too hot, thermal throttling will happen = lower performance.

If you have good CPU cooling, AVX shaves off a few mins (~3-4mins, x6 WU).

If not, it's best to run sse2/sse3 only.

As there is no way to control which version of the app gets sent to you, you can modify the following app_info.xml by removing AVX plan and stick it in your
BOINC-DATA/projects/asteroidsathome.net_boinc
folder

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

<!-- SSE2 -->
	<file_info>
		<name>period_search_10210_windows_x86_64__sse2.exe</name>
		<executable/>
	</file_info>
	<app_version>
		<app_name>period_search</app_name>
		<version_num>1021</version_num>
		<avg_ncpus>1.00</avg_ncpus>
		<max_ncpus>1.00</max_ncpus>
		<plan_class>sse2</plan_class>
		<file_ref>
			<file_name>period_search_10210_windows_x86_64__sse2.exe</file_name>
			<main_program/>
		</file_ref>
	</app_version>


<!-- SSE3 -->
	<file_info>
		<name>period_search_10210_windows_x86_64__sse3.exe</name>
		<executable/>
	</file_info>
	<app_version>
		<app_name>period_search</app_name>
		<version_num>1021</version_num>
		<avg_ncpus>1.00</avg_ncpus>
		<max_ncpus>1.00</max_ncpus>
		<plan_class>sse3</plan_class>
		<file_ref>
			<file_name>period_search_10210_windows_x86_64__sse3.exe</file_name>
			<main_program/>
		</file_ref>
	</app_version>


<!-- AVX -->
	<file_info>
		<name>period_search_10210_windows_x86_64__avx.exe</name>
		<executable/>
	</file_info>
	<app_version>
		<app_name>period_search</app_name>
		<version_num>1021</version_num>
		<avg_ncpus>1.00</avg_ncpus>
		<max_ncpus>1.00</max_ncpus>
		<plan_class>avx</plan_class>
		<file_ref>
			<file_name>period_search_10210_windows_x86_64__avx.exe</file_name>
			<main_program/>
		</file_ref>
	</app_version>

</app_info>

Happy crunching!


EDIT: Maybe Radim can possibly offer an option in Preferences page? "Enable AVX computing", perhaps?

---

terencewee*
Sicituradastra.

If someone has Intel Haswell and run AVX version, please post your times.

Thanks
Z

Temps were normal? Are you mixing French and English here? French "temps" translates to English "times" so I think you meant to say "the times were still normal".

@k3ack3r

It's possible to know the times would be normal even without testing. We know IB and SB don't have AVX therefore they cannot benefit from code designed to use AVX. At this time only Haswell CPUs have AVX therefore only Haswell CPUs will run the code faster.

temps = temperatures ;)

SB and Ivy have of course AVX instructions and can be used very efficient with primegrid's llr.

About the detection - scheduler works as it should. The problem is that the current version of BOINC manager doesn't detect avx on all processors that support it. Updated detection is already implemented in BOINC source codes (I don't know if it is already in branch) so when new version of BOINC manager is out it should detect avx on all processors (no related to version of os).

Could be a problem, here is a i5 snippet from 7.2.16

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 tm2 pbe

AVX detection is in source code only, I think. No official build. The only way for now is to use app_info.

If someone has Intel Haswell and run AVX version, please post your times.

i5-4670 - 966 sec.
http://asteroidsathome.net/boinc/workunit.php?wuid=7296844
http://asteroidsathome.net/boinc/workunit.php?wuid=7296827


sse3 was about 1170-1180 sec.
http://asteroidsathome.net/boinc/results.php?hostid=50173

i5-4670 - 966 sec.
http://asteroidsathome.net/boinc/workunit.php?wuid=7296844
http://asteroidsathome.net/boinc/workunit.php?wuid=7296827


sse3 was about 1170-1180 sec.
http://asteroidsathome.net/boinc/results.php?hostid=50173

Nice. As expected. Is it on stock clocks?

Nice. As expected. Is it on stock clocks?

Yeah. No overclocking and TurboBoost disabled. Box cooler :(