Running SETI@home on an nVidia Fermi GPU

Message boards : Number crunching : Running SETI@home on an nVidia Fermi GPU
Message board moderation

To post messages, you must log in.

Previous · 1 . . . 6 · 7 · 8 · 9 · 10 · 11 · 12 . . . 15 · Next

AuthorMessage
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14655
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1006489 - Posted: 20 Jun 2010, 8:32:33 UTC - in response to Message 1006481.  
Last modified: 20 Jun 2010, 9:17:05 UTC

Heres the app info file after I installed Lunatics_Win64v0.36_(SSE3+)_AP505r409_AKv8bx64_CudaV12 using default settings App info file is from project>Seti folder. Is this the right app info file?

It should be, but it doesn't feel right: there's no sign of the CudaV12 you say you selected.

In one way that's good, because CudaV12 isn't compatible with your Fermi: in another way it's bad, because it suggests that there may be a second project>Seti folder that you haven't found yet.

First things first: check the time stamp on that file you posted. When was it created/modified?

Edit: I've got to go out now, and will be otherwise occupied all day. Could somebody else pick this up and talk Speedy through the next steps, please?
ID: 1006489 · Report as offensive
Profile Questor Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 3 Sep 04
Posts: 471
Credit: 230,506,401
RAC: 157
United Kingdom
Message 1006501 - Posted: 20 Jun 2010, 9:22:21 UTC - in response to Message 1006489.  
Last modified: 20 Jun 2010, 9:23:45 UTC

Heres the app info file after I installed Lunatics_Win64v0.36_(SSE3+)_AP505r409_AKv8bx64_CudaV12 using default settings App info file is from project>Seti folder. Is this the right app info file?

It should be, but it doesn't feel right: there's no sign of the CudaV12 you say you selected.

In one way that's good, because CudaV12 isn't compatible with your Fermi: in another way it's bad, because it suggests that there may be a second project>Seti folder that you haven't found yet.

First things first: check the time stamp on that file you posted. When was it created/modified?



Also your tasks from before 14th shows as anonymous platform but all tasks since show as stock apps - so it doesnt look as though your installation is currently using an app_info file. I dont currently have W7 but ISTR the data being by default under C:\ProgramData\BOINC\ which can be a hidden folder path so you may not be able to browse to it as the user you are logged in as. If so try putting "C:\ProgramData\BOINC" into the path in explorer.
(I remember that from using Reschedule on W7 - you couldn't browse to the path but had to type it in directly)
GPU Users Group



ID: 1006501 · Report as offensive
Speedy
Volunteer tester
Avatar

Send message
Joined: 26 Jun 04
Posts: 1643
Credit: 12,921,799
RAC: 89
New Zealand
Message 1006503 - Posted: 20 Jun 2010, 9:25:30 UTC

app info was created/modifed at 05:20 utc 17:20 New Zealand time. 17:20 was the time I installed ap.
ID: 1006503 · Report as offensive
Josef W. Segur
Volunteer developer
Volunteer tester

Send message
Joined: 30 Oct 99
Posts: 4504
Credit: 1,414,761
RAC: 0
United States
Message 1006591 - Posted: 20 Jun 2010, 15:12:27 UTC - in response to Message 1006503.  

app info was created/modifed at 05:20 utc 17:20 New Zealand time. 17:20 was the time I installed ap.

OK, the default settings gave you the SSE3 MB application and no CUDA application; that seems correct. I would have expected both x86 and x86_64 app_versions, but as you have no "in progress" work that doesn't matter.

Nevertheless, I suggest you uninstall it and then reinstall it selecting the SSSE3x box for the MB application, and either of the CUDA apps. Your Core i7 will run any of the MB versions, either SSSE3x or SSE4.1 would be significantly better than SSE3, and SSSE3x probably slightly better than SSE4.1. Installing one of the CUDA apps will give a section which can be edited or replaced with the similar section for the stock 610 CUDA Fermi information.

If Jason gives different advice, by all means believe it's better than mine. But as it's very early Monday morning where Jason lives, he may be getting some zzzzzzz's.
                                                             Joe
ID: 1006591 · Report as offensive
Profile jason_gee
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 24 Nov 06
Posts: 7489
Credit: 91,093,184
RAC: 0
Australia
Message 1006611 - Posted: 20 Jun 2010, 16:40:46 UTC - in response to Message 1006591.  
Last modified: 20 Jun 2010, 16:52:08 UTC

... But as it's very early Monday morning where Jason lives, he may be getting some zzzzzzz's.
... Ha! Phat Chance of that with all this kerfuffle going on!

I would indeed go the ssse3x (Three S's..ex) unless you have a sooper dooper set of RAM and like splitting hairs enough to tell us if the SSE4.1 build likes your particular i7 or not. [Edit: I do have some i7 specific optimisations in my engineering journal, on the backburner for a while yet, but either AKv8b build should perform better than stock anyway ... a bit ]

@Joe, time to clean your glasses again :P. That correctly shows both x86 & x64 app versions (with the same app)

Jason

[Edit:] BTW, you can safely install over the top, without having to uninstall first.
"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.
ID: 1006611 · Report as offensive
Josef W. Segur
Volunteer developer
Volunteer tester

Send message
Joined: 30 Oct 99
Posts: 4504
Credit: 1,414,761
RAC: 0
United States
Message 1006634 - Posted: 20 Jun 2010, 18:09:55 UTC - in response to Message 1006611.  

... But as it's very early Monday morning where Jason lives, he may be getting some zzzzzzz's.
... Ha! Phat Chance of that with all this kerfuffle going on!

I would indeed go the ssse3x (Three S's..ex) unless you have a sooper dooper set of RAM and like splitting hairs enough to tell us if the SSE4.1 build likes your particular i7 or not. [Edit: I do have some i7 specific optimisations in my engineering journal, on the backburner for a while yet, but either AKv8b build should perform better than stock anyway ... a bit ]

@Joe, time to clean your glasses again :P. That correctly shows both x86 & x64 app versions (with the same app)

Jason

[Edit:] BTW, you can safely install over the top, without having to uninstall first.

Darn, I just washed the glasses yesterday!

The reason I recommended the uninstall then reinstall pair was so Speedy could conveniently go back to stock if needed. Shouldn't matter much, the stock files would be preserved in oldApp_backup either way. And Speedy probably has much better connectivity to Berkeley than I, so redownloading the files wouldn't take long. OTOH, I understand connectivity from New Zealand to the rest of the world often involves paying a premium for anything beyond a specific amount per month.
                                                             Joe
ID: 1006634 · Report as offensive
Speedy
Volunteer tester
Avatar

Send message
Joined: 26 Jun 04
Posts: 1643
Credit: 12,921,799
RAC: 89
New Zealand
Message 1006771 - Posted: 21 Jun 2010, 3:23:06 UTC

As per Joes guideness I've installed SSSEX app with the faster cuda dlls.


<app_info>
<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>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>MB_6.08_CUDA_V12_VLARKill_FPLim2048.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>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>1</count>
</coproc>
<file_ref>
<file_name>MB_6.08_CUDA_V12_VLARKill_FPLim2048.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>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</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>1</count>
</coproc>
<file_ref>
<file_name>MB_6.08_CUDA_V12_VLARKill_FPLim2048.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>
</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>1</count>
</coproc>
<file_ref>
<file_name>MB_6.08_CUDA_V12_VLARKill_FPLim2048.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>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</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>1</count>
</coproc>
<file_ref>
<file_name>MB_6.08_CUDA_V12_VLARKill_FPLim2048.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>
</app_version>
</app_info>

What part do I need to copy & what files do I need go get fermi 6.10 app to work?

Thanks in advance
ID: 1006771 · Report as offensive
Speedy
Volunteer tester
Avatar

Send message
Joined: 26 Jun 04
Posts: 1643
Credit: 12,921,799
RAC: 89
New Zealand
Message 1006773 - Posted: 21 Jun 2010, 3:28:00 UTC - in response to Message 1006634.  
Last modified: 21 Jun 2010, 3:33:03 UTC

I understand connectivity from New Zealand to the rest of the world often involves paying a premium for anything beyond a specific amount per month.
                                                             Joe

Yes you are right theres no such thing as a high speed (more than 256/128kb) unlimited cap to my knowledge

If there is can you let me know?
ID: 1006773 · Report as offensive
Josef W. Segur
Volunteer developer
Volunteer tester

Send message
Joined: 30 Oct 99
Posts: 4504
Credit: 1,414,761
RAC: 0
United States
Message 1006793 - Posted: 21 Jun 2010, 5:22:43 UTC - in response to Message 1006771.  

...
What part do I need to copy & what files do I need go get fermi 6.10 app to work?

Thanks in advance

I'm going to let someone with actual experience give the final answer, but replacing cudart.dll with cudart32_30_14.dll, cufft.dll with cufft32_30_14.dll, MB_6.08_CUDA_V12_VLARKill_FPLim2048.exe with setiathome_6.10_windows_intelx86__cuda_fermi.exe, and cuda23 with cuda_fermi are the primary needed changes. There are 5 places for each file name change, two for the plan_class change.

Because you have no "in progress" work on the host the version_num for the cuda_fermi app_versions could have been left at 608, but just to be consistent with what others are using I've changed it to 610 in the following edited app_info.xml.
<app_info>
    <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>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>setiathome_6.10_windows_intelx86__cuda_fermi.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>1</count>
        </coproc>
        <file_ref>
            <file_name>setiathome_6.10_windows_intelx86__cuda_fermi.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>1</count>
        </coproc>
        <file_ref>
            <file_name>setiathome_6.10_windows_intelx86__cuda_fermi.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>1</count>
        </coproc>
        <file_ref>
            <file_name>setiathome_6.10_windows_intelx86__cuda_fermi.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>1</count>
        </coproc>
        <file_ref>
            <file_name>setiathome_6.10_windows_intelx86__cuda_fermi.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>


You'll also need to be sure that the cudart32_30_14.dll, cufft32_30_14.dll, and setiathome_6.10_windows_intelx86__cuda_fermi.exe files are present. The Lunatics installer doesn't remove them, but if you've started BOINC since having an app_info.xml in place it will have removed them. If so, copy them back from the oldApp_backup folder.

Please wait for someone else to check this before trying to use it.
                                                                 Joe
ID: 1006793 · Report as offensive
Profile SciManStev Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 20 Jun 99
Posts: 6653
Credit: 121,090,076
RAC: 0
United States
Message 1006864 - Posted: 21 Jun 2010, 12:52:02 UTC - in response to Message 1006212.  


You have read anonymous platform, haven't you? It doesn't help much with the practical nitty-gritty you're wrestling with here, but it should give you a feel for the shape of how it's supposed to work.


This was very helpful. It gives a few of the variables that can be used. Are there more, and if so is there a complete list? I will be looking through the archives from those 3 lists mentioned later. I am getting an understanding of how things are linked together and controlled. I have now seen a variety of app_info files, and there are definitly consistancies, and big differences. From what I'm seeing, there are several ways they can be written to accomplish the same thing, as long as the basic information is there.

Steve
Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website
ID: 1006864 · Report as offensive
Josef W. Segur
Volunteer developer
Volunteer tester

Send message
Joined: 30 Oct 99
Posts: 4504
Credit: 1,414,761
RAC: 0
United States
Message 1006913 - Posted: 21 Jun 2010, 15:31:20 UTC - in response to Message 1006864.  


You have read anonymous platform, haven't you? It doesn't help much with the practical nitty-gritty you're wrestling with here, but it should give you a feel for the shape of how it's supposed to work.


This was very helpful. It gives a few of the variables that can be used. Are there more, and if so is there a complete list? I will be looking through the archives from those 3 lists mentioned later. I am getting an understanding of how things are linked together and controlled. I have now seen a variety of app_info files, and there are definitly consistancies, and big differences. From what I'm seeing, there are several ways they can be written to accomplish the same thing, as long as the basic information is there.

Steve

There are more, but not a list as such. Essentially, the fact that BOINC is open source means the most detailed documentation is the source code. The overall parsing of app_info.xml is in boinc/client/cs_statefile.cpp and the parsing of <app>, <file_info>, <app_version>, and <file_ref> elements is in boinc/client/client_types.cpp. Of course many other source files would need to be examined to really figure out what effects the variables have.
                                                               Joe
ID: 1006913 · Report as offensive
Profile SciManStev Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 20 Jun 99
Posts: 6653
Credit: 121,090,076
RAC: 0
United States
Message 1006920 - Posted: 21 Jun 2010, 15:45:15 UTC - in response to Message 1006913.  


There are more, but not a list as such. Essentially, the fact that BOINC is open source means the most detailed documentation is the source code. The overall parsing of app_info.xml is in boinc/client/cs_statefile.cpp and the parsing of <app>, <file_info>, <app_version>, and <file_ref> elements is in boinc/client/client_types.cpp. Of course many other source files would need to be examined to really figure out what effects the variables have.
                                                               Joe


Thank you! I will be looking at the source code over the next few days, weeks, months, etc. and see what I can gleam from it. I realize I have a huge learning curve ahead of me, but I'm going to wade right in and test the water. I am fully prepared for mistakes, success, and lots of study. This is really interesting how the whole system is tied together. The more I learn, the more I become intrigued.

Steve
Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website
ID: 1006920 · Report as offensive
TheFreshPrince a.k.a. BlueTooth76
Avatar

Send message
Joined: 4 Jun 99
Posts: 210
Credit: 10,315,944
RAC: 0
Netherlands
Message 1006935 - Posted: 21 Jun 2010, 16:16:31 UTC
Last modified: 21 Jun 2010, 16:18:08 UTC

The "out of disk space" situation has one advantage!

After crunching about 140 WU's I now know they average about 20 minutes and 12 seconds on the GTX470. I didn't calculate the shorties or the 2 WU's that ended after 25 seconds.

The GTX470 is doing 3 at a time, so that gives me an output of about 9 WU's every hour. I thinks that's not bad for a non-optimized app and in the next months there should be room to increase with 20 or 30% (?) if an optimized app comes available (?).
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
ID: 1006935 · Report as offensive
Profile jason_gee
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 24 Nov 06
Posts: 7489
Credit: 91,093,184
RAC: 0
Australia
Message 1006944 - Posted: 21 Jun 2010, 16:35:45 UTC - in response to Message 1006935.  

20 or 30% (?) if an optimized app comes available (?).


Looks like about 10% on Fermi in current experimental builds, available 'soon-ish'. 20% already at low angle ranges. Considering the architecture improvements, likely 20-30% overall in ~1 month, and probably a bit more after the cheaper variants are out (and I can get one :P). That's if nVidia engineers don't beat us to it ( It helps to have the hardware you're working on, and be paid to do it ;) )

Jason
"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.
ID: 1006944 · Report as offensive
Profile SciManStev Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 20 Jun 99
Posts: 6653
Credit: 121,090,076
RAC: 0
United States
Message 1006952 - Posted: 21 Jun 2010, 16:53:47 UTC - in response to Message 1006944.  

20 or 30% (?) if an optimized app comes available (?).


Looks like about 10% on Fermi in current experimental builds, available 'soon-ish'. 20% already at low angle ranges. Considering the architecture improvements, likely 20-30% overall in ~1 month, and probably a bit more after the cheaper variants are out (and I can get one :P). That's if nVidia engineers don't beat us to it ( It helps to have the hardware you're working on, and be paid to do it ;) )

Jason


If I had the resources left after what I built, I would gladly buy one and send it to you. I'm still thinking of a way to do it.

Steve
Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website
ID: 1006952 · Report as offensive
Profile jason_gee
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 24 Nov 06
Posts: 7489
Credit: 91,093,184
RAC: 0
Australia
Message 1006963 - Posted: 21 Jun 2010, 17:16:31 UTC - in response to Message 1006952.  

If I had the resources left after what I built, I would gladly buy one and send it to you. I'm still thinking of a way to do it.

Steve


The current models are a 'bit much' for me in power usage. I reckon when either the 460 or rumoured 475 materialise, I'll have saved enough pennies to grab one (working on it ;) )
"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.
ID: 1006963 · Report as offensive
Speedy
Volunteer tester
Avatar

Send message
Joined: 26 Jun 04
Posts: 1643
Credit: 12,921,799
RAC: 89
New Zealand
Message 1007205 - Posted: 22 Jun 2010, 8:51:38 UTC - in response to Message 1006793.  



Please wait for someone else to check this before trying to use it.
                                                                 Joe

Thanks Joe for your help. I will await more assistance before firing up Seti
ID: 1007205 · Report as offensive
TheFreshPrince a.k.a. BlueTooth76
Avatar

Send message
Joined: 4 Jun 99
Posts: 210
Credit: 10,315,944
RAC: 0
Netherlands
Message 1007332 - Posted: 23 Jun 2010, 10:16:49 UTC
Last modified: 23 Jun 2010, 10:18:08 UTC

Came home yesterday and saw that all my CUDA WU's errored out after 32m17s.
Luckily I made a backup of my Boinc-data and the rig wasn't connected to the internet so it couldn't upload any results.

Put back my backup, removed the FLOPS from the app_info and it didn't happen again :)
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
ID: 1007332 · Report as offensive
Josef W. Segur
Volunteer developer
Volunteer tester

Send message
Joined: 30 Oct 99
Posts: 4504
Credit: 1,414,761
RAC: 0
United States
Message 1007860 - Posted: 24 Jun 2010, 20:34:16 UTC - in response to Message 1007205.  

Please wait for someone else to check this before trying to use it.
                                                                 Joe

Thanks Joe for your help. I will await more assistance before firing up Seti

I'm actually fairly confident I got it right, if it were my machine I'd certainly fire it up now and try for some of the work while the spigot is on. I rather suspect they'll have to turn some capabilities off again, it would be a pity to miss this opportunity.
                                                              Joe
ID: 1007860 · Report as offensive
Profile MusicGod
Avatar

Send message
Joined: 7 Dec 02
Posts: 97
Credit: 24,782,870
RAC: 0
United States
Message 1008643 - Posted: 26 Jun 2010, 15:36:32 UTC

Ok I`m running 8 units at once, is this a bad thing?
All of my cpu`s are working at 100% and my gpu is constantly going.
I`m running an Asus cg9250 i7 core 2.67 gh and 12 gig of memory witha gtx 260 vid card.
ID: 1008643 · Report as offensive
Previous · 1 . . . 6 · 7 · 8 · 9 · 10 · 11 · 12 . . . 15 · Next

Message boards : Number crunching : Running SETI@home on an nVidia Fermi GPU


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.