I have jut restarted MW after the last Optimized apps were dropped arounf April time.

I have just reattached to MW and using the stock apps on a Win7 64bit with GTX460

Are the stock apps optimised versions or are there going to be NEW optimized version coming soon especially for CUDA


I want to run 2 WU on my GTX460, the current stock app is only running one WU on the GTX460, can some one provide an app_info.xml file for the stock apps so I can modify the CUDA count to allow 2 WU

Thanks

I have jut restarted MW after the last Optimized apps were dropped arounf April time.

I have just reattached to MW and using the stock apps on a Win7 64bit with GTX460

Are the stock apps optimised versions or are there going to be NEW optimized version coming soon especially for CUDA

Just the past week a 'optimized' stock app was released. I am down to 9-10 hours on my P4 Xp for the de_separation_13_3s tasks. A large improvement over the previous app. Still seems slightly slower than the old Opti apps.

I want to run 2 WU on my GTX460, the current stock app is only running one WU on the GTX460, can some one provide an app_info.xml file for the stock apps so I can modify the CUDA count to allow 2 WU

Thanks

I know it was posted somewhere.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

<app_info>
  <app>
    <name>milkyway</name>
  </app>
  <file_info>
    <name>milkyway_separation_0.82_windows_intelx86__cuda_opencl.exe</name>
    <executable />
  </file_info>
  <app_version>
    <app_name>milkyway</app_name>
    <version_num>82</version_num>
    <flops>1.0e11</flops>
    <avg_ncpus>0.05</avg_ncpus>
    <max_ncpus>1</max_ncpus>
    <plan_class>cuda</plan_class>
    <coproc>
      <type>CUDA</type>
      <count>1</count>
    </coproc>
	<cmdline></cmdline>
    <file_ref>
      <file_name>milkyway_separation_0.82_windows_intelx86__cuda_opencl.exe</file_name>
      <main_program/>
    </file_ref>
  </app_version>
</app_info>

New features:
- Faster CPU calculations because of SSE2 intrinsics from Crunch3r. This should get a bit faster later when I get to some other stuff.

- The binaries now include the different SSE levels for the critical function (e.g. x87/SSE2/SSE3) all in one, and will use the appropriate one for the detected CPU's capabilities, so you don't need any special __sse2 version or anything. The problems on systems without SSE2 which happened sometimes for the GPU applications should also be fixed.

- Checkpointing for GPUs for both OpenCL/Nvidia and ATI/AMD for CAL. It will checkpoint no more frequently than after at least 10% progress, so it might not checkpoint as frequently as your settings specify if you have a particularly slow GPU. GPU checkpointing is a bit slow when it does happen, so if you don't want it, you can disable it with the flag --gpu-disable-checkpointing.

- The Nvidia OpenCL platform should now always be used avoiding issues if you had both AMD's and Nvidia's installed

- More reliable chunking for different GPUs. I didn't play with the time estimates so much, but I think the actual run times should now be closer to the estimates. There should also be fewer cases where a GPU will end up using the slowest possible work size option. I'll probably have to fiddle with this some more if people still aren't happy with the lag.

- Work around for a Catalyst driver problem where sometimes the GPU was reported as 0 Mhz, resulting in much more lag which I think was some peoples' problem.

- New flag that some people requested: --process-priority (-b). On Windows this is 0 (lowest) - 4 (highest) for overriding the process priority. On Linux this is the nice value.

- CAL specific: Removed --responsiveness-factor flag. Use --gpu-target-frequency or --non-responsive instead depending on what you want to do.

- Actually updated the 32-bit OS X application

- In the event of a crash on Windows, you should no longer be bothered with useless crash dialogs

---

Thanks, after a bit of searching I found these OPTI apps on your site.

I did notice a mistake with the downloaded Win64bit CPU files, in the app_info for the CPU version you are missing a < from the ending tag of name for the first opti app. see below. Upon running BOINC it complained about the missing app and delete it, upon placing the < into the file makes it work.

<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_0.88_windows_x86_64.exe/name>
<executable />
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>88</version_num>
<cmdline></cmdline>
<file_ref>
<file_name>milkyway_separation_0.88_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

<app_info>
  <app>
    <name>milkyway</name>
  </app>
  <file_info>
    <name>milkyway_separation_0.82_windows_intelx86__cuda_opencl.exe</name>
    <executable />
  </file_info>
  <app_version>
    <app_name>milkyway</app_name>
    <version_num>82</version_num>
    <flops>1.0e11</flops>
    <avg_ncpus>0.05</avg_ncpus>
    <max_ncpus>1</max_ncpus>
    <plan_class>cuda</plan_class>
    <coproc>
      <type>CUDA</type>
      <count>1</count>
    </coproc>
	<cmdline></cmdline>
    <file_ref>
      <file_name>milkyway_separation_0.82_windows_intelx86__cuda_opencl.exe</file_name>
      <main_program/>
    </file_ref>
  </app_version>
</app_info>

New features:
- Faster CPU calculations because of SSE2 intrinsics from Crunch3r. This should get a bit faster later when I get to some other stuff.

- The binaries now include the different SSE levels for the critical function (e.g. x87/SSE2/SSE3) all in one, and will use the appropriate one for the detected CPU's capabilities, so you don't need any special __sse2 version or anything. The problems on systems without SSE2 which happened sometimes for the GPU applications should also be fixed.

- Checkpointing for GPUs for both OpenCL/Nvidia and ATI/AMD for CAL. It will checkpoint no more frequently than after at least 10% progress, so it might not checkpoint as frequently as your settings specify if you have a particularly slow GPU. GPU checkpointing is a bit slow when it does happen, so if you don't want it, you can disable it with the flag --gpu-disable-checkpointing.

- The Nvidia OpenCL platform should now always be used avoiding issues if you had both AMD's and Nvidia's installed

- More reliable chunking for different GPUs. I didn't play with the time estimates so much, but I think the actual run times should now be closer to the estimates. There should also be fewer cases where a GPU will end up using the slowest possible work size option. I'll probably have to fiddle with this some more if people still aren't happy with the lag.

- Work around for a Catalyst driver problem where sometimes the GPU was reported as 0 Mhz, resulting in much more lag which I think was some peoples' problem.

- New flag that some people requested: --process-priority (-b). On Windows this is 0 (lowest) - 4 (highest) for overriding the process priority. On Linux this is the nice value.

- CAL specific: Removed --responsiveness-factor flag. Use --gpu-target-frequency or --non-responsive instead depending on what you want to do.

- Actually updated the 32-bit OS X application

- In the event of a crash on Windows, you should no longer be bothered with useless crash dialogs

That is what happens when you are copying and pasting names quickly.

---

Just the past week a 'optimized' stock app was released. I am down to 9-10 hours on my P4 Xp for the de_separation_13_3s tasks. A large improvement over the previous app. Still seems slightly slower than the old Opti apps.

Yes, the new stock opti apps are slower. The stock app is using a dispatcher that chooses a code path (SSE level) which is supported on your CPU and the rest of the code is not optimized at all.

(The whole new build system is also preventing me from releasing some more tuned binaries using the intel compiler etc... it's a real pain in the ass and i hate that cmake crap!!)

A major part of the optimizations is still missing, hopfully Matt will find the time to integrate it into the stock app. That one will boost performance again and should outperform the old optimized cpu apps by a few percent.

---

Join Support science! Joinc Team BOINC United now!

Here's a 'optimized' CPU app which was compiled using the Intel(R) C++ Compiler XE 12.0.4.196 for Windows.

A SSE2 compatible CPU is required (AMD & Intel)!
Difference is that we're using Intels LibM especially the exp(e^x) function, which is faster than the 'stock' SSE2 polyn. eval....

download -> MilkyWay Separation SSE2 Intel&AMD

---

Join Support science! Joinc Team BOINC United now!

When I use the app_info.xml, must there also be an entry for the N-body in it?

When I use the app_info.xml, must there also be an entry for the N-body in it?

You don't have to run n-body at all (why isn't it possible in the user prefs to disable n-body ???).

The included app-info.xml doesn't have an entry for n-body so you're only going to run separation WUs.

---

Join Support science! Joinc Team BOINC United now!

You don't have to run n-body at all (why isn't it possible in the user prefs to disable n-body ???).

Ähm I'm a little confused about that - why should't I do n-body wu's?
When they pay less - that's not a reason, somebody has to do it.

Here's a 'optimized' CPU app which was compiled using the Intel(R) C++ Compiler XE 12.0.4.196 for Windows.

A SSE2 compatible CPU is required (AMD & Intel)!
Difference is that we're using Intels LibM especially the exp(e^x) function, which is faster than the 'stock' SSE2 polyn. eval....

download -> MilkyWay Separation SSE2 Intel&AMD

I am getting a 404 when i'm trying to download that opti app.

Here's a 'optimized' CPU app which was compiled using the Intel(R) C++ Compiler XE 12.0.4.196 for Windows.

A SSE2 compatible CPU is required (AMD & Intel)!
Difference is that we're using Intels LibM especially the exp(e^x) function, which is faster than the 'stock' SSE2 polyn. eval....

download -> MilkyWay Separation SSE2 Intel&AMD

Can you do a Win 32bit ATI version with that actual code version too? Would be great to have the working initial wait, which is in the code since v0.88.

The new opti app (0.91) performes good. I watched an increase of performance up to 8% on my old XEON's.

thx a lot.
But today the download link is empty - why?

greetings Franz

The new opti app (0.91) performes good. I watched an increase of performance up to 8% on my old XEON's.

thx a lot.
But today the download link is empty - why?

greetings Franz

Downloaded too many times?

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

I think I know!!

They get all invalid :-(

I return to stock app.

(The whole new build system is also preventing me from releasing some more tuned binaries using the intel compiler etc... it's a real pain in the ass and i hate that cmake crap!!)

It shouldn't be. If you have a problem building with ICC I'll fix it.

I think I know!!

They get all invalid :-(

I return to stock app.

Yes, that's why i pulled the download...(and sorry for the long time it took me to reply).. anyway with a propper solution file for MS VS without having to digg through useless cmake txt CRAP files that can't even generate proper makefiles without crashing/erroring out using the latest cmake downloads, it was just a guessing game miswsing some vital config parameters (TG Math... yeah, we got that using ICC and MW_SINCOS is computing CRAP using ICC...)...

Anyway... while digging through this unessassary cmake txt file BS... i finally got it working,linking and validating....

(if anyone want's to compile the code using a proper VS solution project (2005 or 2010)without the retarded hassle to digg through useless cmake txt files... let me know... i'll upload them to ease the pain i was ging through to get everything compiled and linked...)

So.. now that it works... we got a few new apps supporting Intel SSE4.1, Intel SSE3 and Intel/AMD SSE2 (PENTIUM4_SSE2 and AMD SSE2)

for those that know code take a look at -> http://board.mpits.net/viewtopic.php?f=32&t=77.. that one includes source code that replaces the stock 0.91 source from github (should hopefully be integratated in the next stock source code...!(Matt, that's your part :p))

Anyway...
all new optimized apps are linked, downloadable at http://www.mpits.net/opt_mw.php
(do not hotlink the zip files or modify them without permission!!!)

Optimized apps for Pentium4 (SSE2/SSE3) and AMD CPUs using AMD_SSE2 tuned ops(K8,K10) will be added tomorrow... stay tuned and look at http://www.mpits.net/opt_mw.php or http://board.mpits.net/viewtopic.php?f=32&t=77 for updates!!!

Changelog:

- NEW using GROMACS exp_pd function for SSE2 and SSE4.1(addidional 5% faster)(see code)

- NEW using _mm_fsqrt_pd (SSE approx. converting to SSE1(RCP_SRQT) and SSE2 newton raphson stuff... up to 52 bit precission) (see code)

- NEW using PENTIUM4 _mm_div_pd replacement function (see code)

- NEW, faster AMD_SSE(K8,K9,K10) _mm_div_pd replacement (see code)

JOIN BOINC United to get exclusive access to new prelelease optimized GPU & CPU apps!

---

Join Support science! Joinc Team BOINC United now!

My own machines:

Dual Quad Xeon 5365 ES (8 cores)-> SSE3 app -> http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=62008

Core i3 @ 2.13 GHz / HT enabled (4 threads) SSE4.1 app -> http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=281287

---

Join Support science! Joinc Team BOINC United now!

I too show a 404 error for the optimized link to 4.1 and 4.2 compatible Chipset.
I downloaded the sse3 for now till it is fixed.
Or should just I keep the version optimized v0.88 for now?


Well..... rendered about 8 unusable. Reverted back to 0.88 for now until it finishes the rest.
I have a NVidia GTX 285 and a Q9550 processor.....

I also plan on reutilizing my 2nd computer that has a ATI 4870 running the old 0.19 apps on it. It did quite great but I disconnected it a while ago for basement reno. Can I just restart it and running it again or this is all obsolete stuff now?

Martin

I'll test it on one of my machines and than i give feedback in a few hours.

greetings

Franz