- stats on downloads page shows that 32-bit windows non-SSE version of my app was downloaded 12 times, so there is some need for it.

So, with sse2, avx, fma, any modern computer will get the three applications and eventually decide which one is the best one...

Potential problem: some machines error the WUs with avx and fma while sse2 seems to work with everthing I've tried.
I've found that fma can be slightly faster than the sse2 version on some machines but the difference is small.

What OS do you use? AVX needs support on OS side too. List of supported OSes is here: https://en.wikipedia.org/wiki/Advanced_Vector_Extensions#Operating_system_support

So, with sse2, avx, fma, any modern computer will get the three applications and eventually decide which one is the best one...

Potential problem: some machines error the WUs with avx and fma while sse2 seems to work with everthing I've tried.
I've found that fma can be slightly faster than the sse2 version on some machines but the difference is small.

What OS do you use? AVX needs support on OS side too. List of supported OSes is here: https://en.wikipedia.org/wiki/Advanced_Vector_Extensions#Operating_system_support

All machines are Win7-64.

Do you have SP1 installed? AVX support was added in it.

I checked your computers and found few validations errors, but no error reported by app or BOINC client that something was wrong. Maybe these are caused by that mysterious error mentioned by valterc before? I also saw this few times but on SSE version. That was on machine running 24/7 and BOINC configured with long task switch time, so these WUs were crunched from start to end without interruptions. One of them was also crunched by someone with my app and that for that person it was validated successfully, so it is even more interesting.

Hi

you mention the deployment of the new version 0.10 of the application "for all platforms" (this says the news in the boinc manager) however Mac OS is still the old version.

Is this temporary or won't you consider Mac OS (X/macOS) ?


On my Mac I have

Ven 13 jan 23:56:51 2017 | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clfsh ds acpi mmx fxsr sse sse2 ss htt tm pbe pni dtes64 mon dscpl vmx smx est tm2 ssse3 cx16 tpr pdcm sse4_1 sse4_2 popcnt


Would it be compatible with the new version ?

Thanks

You mentioned errors with AVX app. Are they problems with starting/running app, or validation errors? If with starting/running, could you provide me link to example failed WU? I would like to check if there are some details which may be helpful.

Immediate failure. I tested on 12/25 and those WUs are out of the database. On most machines the avx app ran but wasn't any faster (often slower) than the sse2 app. In fact I found no machines on which the avx app was superior. The fma app was a little bit faster than the other 2 versions on my AMD X8 boxes.

Be aware you need a capable cpu to run those applications. Looking at your computers, ony AMD FX have both avx and fma, Athlon 5350 have only avx. however, they are not known to be excellent in these capabilities :)

Is this temporary or won't you consider Mac OS (X/macOS) ?

We will continue to support Mac OS (sse, avx and fma). We just need more time for building the applications (lack of hardware is the main problem).

when I am resetting the project it is not downloading the app to run the WU's. It is just downloading WU's and the erroring out with computational error.

I have been able to get it to download the apps with a detach/reattach. Initially it was running avx @ ~1hr45min a wu but now it is running ver9 at 4 hours a wu. Is there a reason it back leveled to the old app?

app_info was deleted. I did not stop the boinc service though, I just hit reset after deleting app_info. I will try again on a different machine and see if it makes a difference.

Thanks for the work everyone did on this app, I really appreciate it.

Funny how when I follow the directions it works correctly ;)


Thanks for your help

My Windows 10 i7-6700K @ 4.00GHz system is hyper-threaded to 8 cores. When Gene Network Application 0.10 windows_x86_64 was released it was initially only running the avx version (65 tasks). That was followed by a spell running the sse2 version (38 tasks) and its current work allocation has 29 tasks running the fme version. Performance figures so far are:

• 65 completed avx tasks:
  
  
  
  • Average run time 43:11 (min 41:09, max 49:50)
    
  • Average CPU time 42:10 (min 40:54, max 43:53)
    

  
  

• 38 completed sse2 tasks:
  
  
  
  • Average run time 45:04 (min 43:42, max 46:36)
    
  • Average CPU time 44:25 (min 43:01, max 46:13
    

  
  

• 9 completed fme tasks:
  
  
  
  • Average run time 41:31 (min 40:02, max 42:33)
    
  • Average CPU time 40:48 (min 39:45, max 41:43)
    

CPU time gives a more realistic indication of the performance (the avx task with run time 49:50 had CPU time 42:18), and at the moment the timings are pointing towards the fme version being the fastest on that computer (the sample size is too small to say that it's statistically significant, but the minimum and maximum CPU times suggest that's likely to be the case).
____________
"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer