Here is a picture, running 2 x SETI MB tasks.



I don't know the AR of these cause I'll run allMB tasks with the GPU.
Speed heavily depending on AR.

B.t.w. it's a GTX470 (stock), it can run 3 at a time but, I prefer 2, cause no overheating or other issues, read faults ;-)

And this page is again, gettin rather long......

---

Way to go Fred, any idea how much power is been pulled at the plug?

---

This rig uses ~275-320 Watt/hour, depending on the load of the 470.
Only my ATI 5770 &4850 rig, uses more, 380-410 Watt. (If both cards are used)

---

hi Sutaru , you asked about timings of VLAR's on the 470, the first 2 results were VLAR (0.0106 &0.0109), but results are already deleted.
Tomorrow I'll have a look at my MB tasks and have quite a lot (>1200)
of them, if a VLAR is present.
(I thought that a VLAR took ~4000 & 200 CPU seconds, but I'll check, cause I don't know for sure.)

---

About an hour on 470@default.

---

Hi I went over to window 64 bit with v.37 and cannot find my app_info.xml file any more where it go?

Hi I went over to window 64 bit with v.37 and cannot find my app_info.xml file any more where it go?

C:\ProgramData\BOINC\projects\setiathome.berkeley.edu

The folder "ProgramData" is hidden by default so you can't see it with standard settings.
In explorer you can unhide hidden system folders and files.

A "howto":

http://www.sevenforums.com/tutorials/394-hidden-files-folders-show-hide.html

---

Rig name: "x6Crunchy"
OS: Win 7 x64
MB: Asus M4N98TD EVO
CPU: AMD X6 1055T 2.8(1,2v)
GPU: 2x Asus GTX560ti
Member of: Dutch Power Cows

I have tested with a GTX460 and after 3 days I can tell you I stick to my GTX470 and just ordered a second GTX470.

The GTX460 is about 30-35 slower... But, it also is a lot cooler (57C vs 73C).
Powerconsumption is around 100 - 120 Watts... Not bad but I want a little more performance ;)

I found out that running 2 tasks is little faster on the GTX460 and 3 tasks is a bit faster on my GTX470, so it would be hard to have them both in one system anyway.

---

Rig name: "x6Crunchy"
OS: Win 7 x64
MB: Asus M4N98TD EVO
CPU: AMD X6 1055T 2.8(1,2v)
GPU: 2x Asus GTX560ti
Member of: Dutch Power Cows

Got my second GTX470 yesterday.
Same card (Asus ENGTX470) and overclocks with the same settings.
No problems for now :)

The Watt-meter turned into a WTF-meter... 600Watts running Seti...

---

Rig name: "x6Crunchy"
OS: Win 7 x64
MB: Asus M4N98TD EVO
CPU: AMD X6 1055T 2.8(1,2v)
GPU: 2x Asus GTX560ti
Member of: Dutch Power Cows

This may be off topic, but I have to ask ... so here goes. I am thinking of adding a fermi card (EVGA GTS450) < $200, to my newest machine which already has an EVGA GTX275 w/ integrated GTS250, which are two separate physical processors on a single card.

When will the stock apps be able to handle fermi without having to install the optimized apps?

It is my understanding that in order to run the optimized apps that additional software has to be purchased, Microsoft Visual Studio (C++) & Intel's compiler and library packages. I am on a very strict budget and cannot afford the additional software at this time.

Currently have:
Core i7/903/DPX58SO, 6Gb ram, EVGA GTX275/GTS250, Ultra 1200-watt modular PSU

Ok, first, the stock apps can handle Fermi, you just won't be able to run more than one WU at a time without the opt-apps.

Second, you don't need any extra software to run the opt-apps. Just download the installer, run it and watch them go. You should download and run CPU-Z though to make sure what instruction set to choose. It's free. (I would guess you should be able to run SSSE 3 or SSE 4.1.) We leave the Visual Studio and Compiler and Library packages to the guys at Lunatic's. They are the ones that make all these packages.

Third, right now if you keep the other cards you won't be able to run more than one WU on each card because the 250 and the 275 can't handle more than one at a time and there is no way yet to tell each card to do something different.

Hope that answers your questions. If I'm mistaken on any of this I'm sure someone will come along and correct me.

---

PROUD MEMBER OF Team Starfire World BOINC

Ok, first, the stock apps can handle Fermi, you just won't be able to run more than one WU at a time without the opt-apps.

Second, you don't need any extra software to run the opt-apps. Just download the installer, run it and watch them go. You should download and run CPU-Z though to make sure what instruction set to choose. It's free. (I would guess you should be able to run SSSE 3 or SSE 4.1.) We leave the Visual Studio and Compiler and Library packages to the guys at Lunatic's. They are the ones that make all these packages.

Third, right now if you keep the other cards you won't be able to run more than one WU on each card because the 250 and the 275 can't handle more than one at a time and there is no way yet to tell each card to do something different.

Hope that answers your questions. If I'm mistaken on any of this I'm sure someone will come along and correct me.

Thanks Perryjay!! Sorry to take so long to get back to you, but everything went south just as I hit the post button, didn't even know if my question made it. I will go to the Lunatic's page and d/l the installer and go from there. I am not worried about the combined GTX275/GTS250 card as it is already doing what it is supposed to do. I was mainly concerned about the proposed GTS450.

Thanks again.

Hi MaGNeT,
anything additional todo in the appinfo.xml with 2 GTX470 ?
16.10.2010 17:11:41 NVIDIA GPU 0: GeForce GTX 470 (driver version 25896, CUDA version 3010, compute capability 2.0, 1248MB, 726 GFLOPS peak)
16.10.2010 17:11:41 NVIDIA GPU 1: GeForce GTX 470 (driver version 25896, CUDA version 3010, compute capability 2.0, 1249MB, 726 GFLOPS peak)
~~~~~~~~~
<app_info>
<app>
<name>astropulse_v505</name>
</app>
<file_info>
<name>ap_5.05r409_SSE.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>ap_5.05r409_SSE.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>ap_5.05r409_SSE.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b_win_x64_SSSE3x.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>AK_v8b_win_x64_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>AK_v8b_win_x64_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>Lunatics_x32f_win32_cuda30_preview.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_30_14.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_30_14.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>608</version_num>
<platform>windows_intelx86</platform>
<plan_class>cuda</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.48</count>
</coproc>
<file_ref>
<file_name>Lunatics_x32f_win32_cuda30_preview.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>609</version_num>
<platform>windows_intelx86</platform>
<plan_class>cuda23</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.48</count>
</coproc>
<file_ref>
<file_name>Lunatics_x32f_win32_cuda30_preview.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_intelx86</platform>
<plan_class>cuda_fermi</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.48</count>
</coproc>
<file_ref>
<file_name>Lunatics_x32f_win32_cuda30_preview.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_x86_64</platform>
<plan_class>cuda</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.48</count>
</coproc>
<file_ref>
<file_name>Lunatics_x32f_win32_cuda30_preview.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>609</version_num>
<platform>windows_x86_64</platform>
<plan_class>cuda23</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.48</count>
</coproc>
<file_ref>
<file_name>Lunatics_x32f_win32_cuda30_preview.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_x86_64</platform>
<plan_class>cuda_fermi</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.48</count>
</coproc>
<file_ref>
<file_name>Lunatics_x32f_win32_cuda30_preview.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
</app_info>
~~~~~~~~~~~~~~~~~~~~~~~~~~~
are additional entries for the second GPU necesary ?

heinz

---

D5400XS V8-Xeon

_heinz, the app_info is fine as it is, you don't need any extra entries for a second GPU,

Claggy

Me, I have app_info file attached, and I do not understand why I did not receive 6.10 units Fermi ? I only receives 6.08 ...

<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b_win_x64_SSE41.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>AK_v8b_win_x64_SSE41.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>AK_v8b_win_x64_SSE41.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v505</name>
</app>
<file_info>
<name>ap_5.05r409_SSE.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>ap_5.05r409_SSE.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>ap_5.05r409_SSE.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>Lunatics_x32f_win32_cuda30_preview.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_30_14.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_30_14.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>608</version_num>
<platform>windows_intelx86</platform>
<plan_class>cuda</plan_class>
<avg_ncpus>0.100000</avg_ncpus>
<max_ncpus>0.100000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>Lunatics_x32f_win32_cuda30_preview.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>609</version_num>
<platform>windows_intelx86</platform>
<plan_class>cuda23</plan_class>
<avg_ncpus>0.100000</avg_ncpus>
<max_ncpus>0.100000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>Lunatics_x32f_win32_cuda30_preview.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_intelx86</platform>
<plan_class>cuda_fermi</plan_class>
<avg_ncpus>0.100000</avg_ncpus>
<max_ncpus>0.100000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>Lunatics_x32f_win32_cuda30_preview.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_x86_64</platform>
<plan_class>cuda</plan_class>
<avg_ncpus>0.100000</avg_ncpus>
<max_ncpus>0.100000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>Lunatics_x32f_win32_cuda30_preview.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>609</version_num>
<platform>windows_x86_64</platform>
<plan_class>cuda23</plan_class>
<avg_ncpus>0.100000</avg_ncpus>
<max_ncpus>0.100000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>Lunatics_x32f_win32_cuda30_preview.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_x86_64</platform>
<plan_class>cuda_fermi</plan_class>
<avg_ncpus>0.100000</avg_ncpus>
<max_ncpus>0.100000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>Lunatics_x32f_win32_cuda30_preview.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
</app_info>

---

Alliance Francophone

Me, I have app_info file attached, and I do not understand why I did not receive 6.10 units Fermi ? I only receives 6.08 ...

You don't. You get WUs - period. It makes no difference what your client calls them.

Your app_info specifies that you process all WUs issued for CUDA processing with Lunatics_x32f_win32_cuda30_preview.exe: that's good, you'll use an efficient program, whatever number it's labelled with. Just let them run - you can't do better than that.

Thank you for your reply.

Other question:

So the 6.8 that I receive are calculated as soon as the units Fermi 6.10?

---

Alliance Francophone

They are the same WUs. They will be processed, in the order they are issued by the project, using your graphics card and the most efficient application available. You're good to go: don't worry about it.

Ok, thanks You

---

Alliance Francophone

There are new drivers on the Nvidia website as of October 18, 2010

Version: 260.89 WHQL
Release Date: 2010.10.18

---