+- +-
Say hello if visiting :) by Gecko
11 Jan 2023, 07:43:05 pm

Seti is down again by Mike
09 Aug 2017, 10:02:44 am

Some considerations regarding OpenCL MultiBeam app tuning from algorithm view by Raistmer
11 Dec 2016, 06:30:56 am

Loading APU to the limit: performance considerations by Mike
05 Nov 2016, 06:49:26 am

Better sleep on Windows - new round by Raistmer
26 Aug 2016, 02:02:31 pm

Author Topic: V10/11 of modified SETI MB CUDA + opt AP package for full multi-GPU+CPU use  (Read 233185 times)

Offline Raistmer

  • Working Code Wizard
  • Volunteer Developer
  • Knight who says 'Ni!'
  • *****
  • Posts: 14349
Hi everyone. I have a quick question. If I try the package with 6.6.20 will I need to edit app_info to include flops (or edit it in any other way for that matter), or will it just be enough to do what's said in the first post?

thanks


--
Orin

my PC


There is two ways to achieve the same goal (use all 3 opt apps for crunching).
Either by using my V10 pack or by using BOINC 6.6.14 and up with corresponding app info file.
If you have no problems with BOINC 6.6.20 itself the second way is better that is, with BOINC 6.6.20 you need ONLY CUDA MB part of V10 pack (or even better, V10/11 update, I will post it to first page too soon. For now search this thread). Correct app_info you can take from this thread on SETI main forum:
http://setiathome.berkeley.edu/forum_thread.php?id=52589

And don't forget to  remove cc_config.xml file when you end using "team" pack. It was only temporary solution until BOINC can't do CUDA scheduling correctly. Now BOINC repaired so - no need to use team pack anymore. Only CUDA opt app could be used still cause it gives some performance increase over stock one.

fusion2905

  • Guest
There is two ways to achieve the same goal (use all 3 opt apps for crunching).
Either by using my V10 pack or by using BOINC 6.6.14 and up with corresponding app info file.
If you have no problems with BOINC 6.6.20 itself the second way is better that is, with BOINC 6.6.20 you need ONLY CUDA MB part of V10 pack (or even better, V10/11 update, I will post it to first page too soon. For now search this thread).

This one, right? What about AK_v8b_win_SSE3_AMD_GPU_CPU_team_V10.exe and AP apps? Do i take them from v10 package, or do I just skip them?

Quote
Correct app_info you can take from this thread on SETI main forum:
http://setiathome.berkeley.edu/forum_thread.php?id=52589

Allright, I'll give it a go.

Thanks Raistmer

--
Orin
« Last Edit: 05 Apr 2009, 05:04:24 pm by fusion2905 »

frigens

  • Guest
I've tried to use this mod version on S@H CUDA WU but always get computation error within 30 secs. Not sure what I have done wrong. Is there any place I can retrieve the log of this error WU?

Offline Claggy

  • Alpha Tester
  • Knight who says 'Ni!'
  • ***
  • Posts: 3111
    • My computers at Seti Beta
I've tried to use this mod version on S@H CUDA WU but always get computation error within 30 secs. Not sure what I have done wrong. Is there any place I can retrieve the log of this error WU?

Read Raistmer's post two before yours since you are also using Boinc 6.6.20,

I assume this is the host you're talking about:

hostid=4852276

And Please Stop using Optimised Astropulse 5.00 r103 on Seti Beta, It' doesn't validate with 5.03 on Seti Main, and it sure Won't Validate with AP 5.04 or 5.05

hostid=39303

Claggy

frigens

  • Guest
I've tried to use this mod version on S@H CUDA WU but always get computation error within 30 secs. Not sure what I have done wrong. Is there any place I can retrieve the log of this error WU?

Read Raistmer's post two before yours since you are also using Boinc 6.6.20,

I assume this is the host you're talking about:

hostid=4852276

And Please Stop using Optimised Astropulse 5.00 r103 on Seti Beta, It' doesn't validate with 5.03 on Seti Main, and it sure Won't Validate with AP 5.04 or 5.05

hostid=39303

Claggy

Is that mean I should delete any reference line that link to the CPU app in my app_info? I've attcahed my current app_info as below.

<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<platform>windows_intelx86</platform>
<flops>7285841676</flops>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b_win_SSSE3x_GPU_CPU_team_V10.exe</name>
<executable/>
</file_info>
<file_info>
<name>MB_6.08_mod_CPU_team_CUDA.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<flops>4903931897</flops>
<file_ref>
<file_name>AK_v8b_win_SSSE3x_GPU_CPU_team_V10.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.127970</avg_ncpus>
<max_ncpus>0.127970</max_ncpus>
<flops>21200000000</flops>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>MB_6.08_mod_CPU_team_CUDA.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
</app_info>

The second Computer ID isn't mine, I've not crunch SETI beta for a while although part of my rig hasn't been updated to reflect this. I'll try to do that soon. So is there any optimized app that can be used with Beta?

Thanks
frigens

Offline Raistmer

  • Working Code Wizard
  • Volunteer Developer
  • Knight who says 'Ni!'
  • *****
  • Posts: 14349
AK_v8b_win_SSE3_AMD_GPU_CPU_team_V10.exe and AP apps? Do i take them from v10 package, or do I just skip them?

You can take AP app from V10 pack (V503 rev112) it's identical to standalone Lunatics build but should not use AK_v8 "teamed" apps with 6.6.20 and new app_info.
You should replace them with usual AK_v8 apps from Lunatics Download section.

Offline Claggy

  • Alpha Tester
  • Knight who says 'Ni!'
  • ***
  • Posts: 3111
    • My computers at Seti Beta
I've tried to use this mod version on S@H CUDA WU but always get computation error within 30 secs. Not sure what I have done wrong. Is there any place I can retrieve the log of this error WU?

Read Raistmer's post two before yours since you are also using Boinc 6.6.20,

I assume this is the host you're talking about:

hostid=4852276

And Please Stop using Optimised Astropulse 5.00 r103 on Seti Beta, It' doesn't validate with 5.03 on Seti Main, and it sure Won't Validate with AP 5.04 or 5.05

hostid=39303

Claggy

Is that mean I should delete any reference line that link to the CPU app in my app_info? I've attcahed my current app_info as below.

snip

The second Computer ID isn't mine, I've not crunch SETI beta for a while although part of my rig hasn't been updated to reflect this. I'll try to do that soon. So is there any optimized app that can be used with Beta?

Thanks
frigens

Your app_info seems to be missing the first few lines

<app_info>
<app>

You should replace AK_v8b_win_SSSE3x_GPU_CPU_team_V10.exe with the normal SSSE3 app.

Are sure that isn't your host on Beta?, Because it links through to the other hosts on Main.

Claggy
« Last Edit: 06 Apr 2009, 08:30:42 am by Claggy »

fusion2905

  • Guest
Well, everything seems to be working fine now  ;D

Thanks again Raistmer

Out of curiosity though, what kind of temperatures are you guys seeing on your GPU and CPU(s)?


--
Orin


Offline Raistmer

  • Working Code Wizard
  • Volunteer Developer
  • Knight who says 'Ni!'
  • *****
  • Posts: 14349

Out of curiosity though, what kind of temperatures are you guys seeing on your GPU and CPU(s)?

Still in process of OCing, but when I rised shader freq to 1920 and got temp of 62-65C GPU started produce many computation errors and invalid results.
With 1910 and temp around 62C it works OK it seems. Memory on 1110x2 for now, engine freq still untouched on 600MHz.

elec999

  • Guest
With all my CPU and GPU power. I am still getting really bad results.
Thank you

Offline sunu

  • Alpha Tester
  • Knight who says 'Ni!'
  • ***
  • Posts: 771
elec999 is this you?

This machine runs stock apps. You should switch it to optimized apps.

Checking your most powerful machines, you don't seem to have such a high workunit output. Do you use all of their cores? Do you use them all day, every day (24/7)? If you want good RAC and overall credit, you need to run your machines 24/7.

Edit: If you don't have already, upgrade your boinc to 6.6.20, especially those machines with CUDA GPU.
« Last Edit: 07 Apr 2009, 09:31:50 am by sunu »

codeman05

  • Guest
Hey guys, need some help.

I have a i7 920 running with 3x GTX285s (don't worry 1 is on loan ;)). Vista X64. BOINC 6.6.20

I was running the "base" client and getting MB wu's completed in about 10 mins real time per GPU. I've now enabled astropulse and installed this V10 app.

The "number_of_GPUs" file is set to: 3

CC_config is set to:
<cc_config>
<options>
<ncpus>11</ncpus>
</options>
</cc_config>

Now when I restarted BOINC, all of my CUDA MB units switched over to standard CPU WU's (8 running) and I do not see any CUDA apps running.  Now whats weird is my GPUs are still seeing a load (not full load) and getting warm.


So...what did I screw up? ;)


Thanks guys



BTW. here is a link to the host details if that helps:
http://setiathome.berkeley.edu/show_host_detail.php?hostid=4864280

« Last Edit: 07 Apr 2009, 11:14:31 pm by codeman05 »

codeman05

  • Guest
So...what did I screw up? ;)

I stand corrected. It does look like I'm using 3 GPUs and 5 logical CPUs...The application column dropped the "(cuda)" designation so that threw me off.

I'm not getting AP units, but I guess as long as the CPUs are also crunching MBs...that's not a problem?


What is odd though is that I was getting to claim ~50 points per MB cuda WU before installing this apt. Now it looks like I'm only getting ~15points per wu.
That sound right?

client is 6.6.20 btw.
« Last Edit: 07 Apr 2009, 11:14:19 pm by codeman05 »

Offline sunu

  • Alpha Tester
  • Knight who says 'Ni!'
  • ***
  • Posts: 771
I'm not getting AP units, but I guess as long as the CPUs are also crunching MBs...that's not a problem?

Have you got an optimized AP app? You've also got to edit accordingly your app_info.xml.


What is odd though is that I was getting to claim ~50 points per CUDA WU before installing this apt. Now it looks like I'm only getting ~15points per wu.
That sound right?

It's just a matter of workunit angle range.

Update your boinc to 6.6.20.

codeman05

  • Guest
Hi Sunu,

Thanks for the help.

I am running 6.6.20, sorry left that out before.
Sounds good, I was thinking it was something to get with the angle, but since it happened at the exact same time I switched over. I wasn't sure.


I did resets the project to see if that would make a difference...I now have 11 WU's running at once rather than 8.

here is my AP info

Quote
- <app_info>
- <app>
  <name>astropulse</name>
  </app>
- <file_info>
  <name>ap_5.00r103_SSE3.exe</name>
  <executable />
  </file_info>
- <app_version>
  <app_name>astropulse</app_name>
  <version_num>500</version_num>
- <file_ref>
  <file_name>ap_5.00r103_SSE3.exe</file_name>
  <main_program />
  </file_ref>
  </app_version>
- <app>
  <name>astropulse_v5</name>
  </app>
- <file_info>
  <name>ap_5.03r112_SSE3.exe</name>
  <executable />
  </file_info>
- <app_version>
  <app_name>astropulse_v5</app_name>
  <version_num>503</version_num>
- <file_ref>
  <file_name>ap_5.03r112_SSE3.exe</file_name>
  <main_program />
  </file_ref>
  </app_version>
- <app>
  <name>setiathome_enhanced</name>
  </app>
- <file_info>
  <name>AK_v8b_win_x64_SSSE3x_GPU_CPU_team_V10.exe</name>
  <executable />
  </file_info>
- <file_info>
  <name>cudart.dll</name>
  <executable />
  </file_info>
- <file_info>
  <name>cufft.dll</name>
  <executable />
  </file_info>
- <file_info>
  <name>libfftw3f-3-1-1a_upx.dll</name>
  <executable />
  </file_info>
- <file_info>
  <name>MB_6.08_mod_CUDA_V10.exe</name>
  <executable />
  </file_info>
- <app_version>
  <app_name>setiathome_enhanced</app_name>
  <version_num>528</version_num>
- <file_ref>
  <file_name>AK_v8b_win_x64_SSSE3x_GPU_CPU_team_V10.exe</file_name>
  <main_program />
  </file_ref>
- <file_ref>
  <file_name>cudart.dll</file_name>
  </file_ref>
- <file_ref>
  <file_name>cufft.dll</file_name>
  </file_ref>
- <file_ref>
  <file_name>libfftw3f-3-1-1a_upx.dll</file_name>
  </file_ref>
- <file_ref>
  <file_name>MB_6.08_mod_CUDA_V10.exe</file_name>
  </file_ref>
  </app_version>
- <app_version>
  <app_name>setiathome_enhanced</app_name>
  <version_num>603</version_num>
- <file_ref>
  <file_name>AK_v8b_win_x64_SSSE3x_GPU_CPU_team_V10.exe</file_name>
  <main_program />
  </file_ref>
- <file_ref>
  <file_name>cudart.dll</file_name>
  </file_ref>
- <file_ref>
  <file_name>cufft.dll</file_name>
  </file_ref>
- <file_ref>
  <file_name>libfftw3f-3-1-1a_upx.dll</file_name>
  </file_ref>
- <file_ref>
  <file_name>MB_6.08_mod_CUDA_V10.exe</file_name>
  </file_ref>
  </app_version>
- <app_version>
  <app_name>setiathome_enhanced</app_name>
  <version_num>607</version_num>
- <file_ref>
  <file_name>AK_v8b_win_x64_SSSE3x_GPU_CPU_team_V10.exe</file_name>
  <main_program />
  </file_ref>
- <file_ref>
  <file_name>cudart.dll</file_name>
  </file_ref>
- <file_ref>
  <file_name>cufft.dll</file_name>
  </file_ref>
- <file_ref>
  <file_name>libfftw3f-3-1-1a_upx.dll</file_name>
  </file_ref>
- <file_ref>
  <file_name>MB_6.08_mod_CUDA_V10.exe</file_name>
  </file_ref>
  </app_version>
- <app_version>
  <app_name>setiathome_enhanced</app_name>
  <version_num>608</version_num>
- <file_ref>
  <file_name>AK_v8b_win_x64_SSSE3x_GPU_CPU_team_V10.exe</file_name>
  <main_program />
  </file_ref>
- <file_ref>
  <file_name>cudart.dll</file_name>
  </file_ref>
- <file_ref>
  <file_name>cufft.dll</file_name>
  </file_ref>
- <file_ref>
  <file_name>libfftw3f-3-1-1a_upx.dll</file_name>
  </file_ref>
- <file_ref>
  <file_name>MB_6.08_mod_CUDA_V10.exe</file_name>
  </file_ref>
  </app_version>
  </app_info>
« Last Edit: 08 Apr 2009, 12:00:18 am by codeman05 »

 

Welcome, Guest.
Please login or register.
 
 
 
Forgot your password?
Members
Total Members: 97
Latest: ToeBee
New This Month: 0
New This Week: 0
New Today: 0
Stats
Total Posts: 59559
Total Topics: 1672
Most Online Today: 355
Most Online Ever: 983
(20 Jan 2020, 03:17:55 pm)
Users Online
Members: 0
Guests: 31
Total: 31
Powered by EzPortal