Posts by IFRS

21) Message boards : Number crunching : Closed *SETI/BOINC Milestones [ v2.0 ] - XXI* Closed (Message 1025987)
Posted 18 Aug 2010 by IFRS
Post:


Oh well, I just join them :)
I have nice friends in here, I guess the team can use my RAC to beat the germans ;)


Welcome aboard! Your RAC will be a huge contribution!

Steve


Thank you Steve! Im enjoying my time at the group already :)
22) Message boards : Number crunching : Closed *SETI/BOINC Milestones [ v2.0 ] - XXI* Closed (Message 1025947)
Posted 18 Aug 2010 by IFRS
Post:
Congratulations to GPU Users Group for getting into the third place in RAC worldwide!

Those guys really are a "rising star"! Just a year ago they/you weren't even in the top 200 and now you are in 54, and RAC they/you also have risen about 50 places!

[edit]
And just in time to edit: also congratulations on breaching the 1,000,000 RAC barier!
[/edit]


Oh well, I just join them :)
I have nice friends in here, I guess the team can use my RAC to beat the germans ;)
23) Message boards : Number crunching : Nvidia undeclocking problem (Message 1025698)
Posted 16 Aug 2010 by IFRS
Post:
Any news on this issue? I still suffer of the underclocking problem on all my machines, no matter the driver used or the card. Sometimes, when a GPU produce a computation error, it will underclock to 2d clock, and sadly my new GTX 460s are doing this too.
The only way I found to prevent this (so far) is using stock clock, as the driver will recover and set stock clock again, but then, all performance gains with oc are wasted.
Any news anyone?


I've posted this solution before , but here it is again: HowTo - Prevent GTX 200 Series Downclocking using RivaTuner. I hope it'll work for you like it did for me !

edit: didn't tested it with fermi card yet.


Oh yes, RT. Sorry my bad Zeus, because I didn´t mention that I use RT and it works.... for one GPU. On multi GPU systems, all the others downclock. And no, it does not work with my 460s :(
So im guessing that there is nothing new on this?
24) Message boards : Number crunching : Nvidia undeclocking problem (Message 1025588)
Posted 16 Aug 2010 by IFRS
Post:
Any news on this issue? I still suffer of the underclocking problem on all my machines, no matter the driver used or the card. Sometimes, when a GPU produce a computation error, it will underclock to 2d clock, and sadly my new GTX 460s are doing this too.
The only way I found to prevent this (so far) is using stock clock, as the driver will recover and set stock clock again, but then, all performance gains with oc are wasted.
Any news anyone?
25) Message boards : Number crunching : Closed *SETI/BOINC Milestones [ v2.0 ] - XXI* Closed (Message 1025559)
Posted 16 Aug 2010 by IFRS
Post:
Congrats Steve! Thats a great RAC for a single rig. My pair of aircooled GTX 460 seems to be just up to the moved GTX 295 or a bit higher, but hey, they will add 25k more to my RAC in a few days... aiming for #3 spot.
26) Message boards : Number crunching : Running SETI@home on an nVidia Fermi GPU (Message 1025402)
Posted 15 Aug 2010 by IFRS
Post:
Well, thank you guys, its always very nice to know that you will find strong support here on this foruns no matter what your problem is.
27) Message boards : Number crunching : Running SETI@home on an nVidia Fermi GPU (Message 1024998)
Posted 14 Aug 2010 by IFRS
Post:
Yeah, it´s working now.... i had a corrupted executable. Ty guys, ty Claggy.
28) Message boards : Number crunching : Running SETI@home on an nVidia Fermi GPU (Message 1024982)
Posted 14 Aug 2010 by IFRS
Post:
Oooops, my bad.. it seems that I have a corrupted downloaded file. More in a few minutes...
29) Message boards : Number crunching : Running SETI@home on an nVidia Fermi GPU (Message 1024967)
Posted 14 Aug 2010 by IFRS
Post:
Hi Claggy. I did a repair installation but it didn´t work. This time im running the 460 sli. Still getting the "Process creation failed" message. Any other ideas?


Post your app_info.xml

Claggy


Yep, I was about to do that. Probably I have a problem i can´t see here. Oh, the files are in he proper folder. Here it goes:

<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.05r339_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.05r339_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.05r339_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>610</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>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>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</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>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>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>
30) Message boards : Number crunching : Running SETI@home on an nVidia Fermi GPU (Message 1024777)
Posted 14 Aug 2010 by IFRS
Post:
Hi Claggy. I did a repair installation but it didn´t work. This time im running the 460 sli. Still getting the "Process creation failed" message. Any other ideas?
31) Message boards : Number crunching : Running SETI@home on an nVidia Fermi GPU (Message 1024079)
Posted 10 Aug 2010 by IFRS
Post:
Hey guys, can anyone tell me what im doing wrong? I just manage to make my system (and cache) survive a win xp32 -> win7 64 upgrade, and was confident to insert Fermi information on it, in preparation for my 2 GTX 460 that are on the way, even still with my GTX 295 installed (its supposed to be backward compatible?).
I reschedule all my WUs to cpu, and when i can get some 610 work now, its ending like this:

09/08/2010 22:31:38 Starting BOINC client version 6.10.58 for windows_x86_64
09/08/2010 22:31:38 log flags: file_xfer, sched_ops, task
09/08/2010 22:31:38 Libraries: libcurl/7.19.7 OpenSSL/0.9.8l zlib/1.2.3
09/08/2010 22:31:38 Data directory: C:\ProgramData\BOINC
09/08/2010 22:31:38 Running under account Casa
09/08/2010 22:31:38 Processor: 4 GenuineIntel Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz [Family 6 Model 26 Stepping 5]
09/08/2010 22:31:38 Processor: 256.00 KB cache
09/08/2010 22:31:38 Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 cx16 sse4_1 sse4_2 syscall lm vmx tm2 popcnt pbe
09/08/2010 22:31:38 OS: Microsoft Windows 7: Ultimate x64 Edition, (06.01.7600.00)
09/08/2010 22:31:38 Memory: 2.99 GB physical, 5.98 GB virtual
09/08/2010 22:31:38 Disk: 232.88 GB total, 198.49 GB free
09/08/2010 22:31:38 Local time is UTC -3 hours
09/08/2010 22:31:38 NVIDIA GPU 0: GeForce GTX 295 (driver version 25896, CUDA version 3010, compute capability 1.3, 879MB, 725 GFLOPS peak)
09/08/2010 22:31:38 NVIDIA GPU 1: GeForce GTX 295 (driver version 25896, CUDA version 3010, compute capability 1.3, 880MB, 596 GFLOPS peak)
09/08/2010 22:31:38 SETI@home Found app_info.xml; using anonymous platform
09/08/2010 22:31:39 SETI@home URL http://setiathome.berkeley.edu/; Computer ID 5482370; resource share 100
09/08/2010 22:31:39 SETI@home General prefs: from SETI@home (last modified 20-Apr-2009 18:19:58)
09/08/2010 22:31:39 SETI@home Computer location: school
09/08/2010 22:31:39 General prefs: using separate prefs for school
09/08/2010 22:31:39 Reading preferences override file
09/08/2010 22:31:39 Preferences:
09/08/2010 22:31:39 max memory usage when active: 1531.06MB
09/08/2010 22:31:39 max memory usage when idle: 2755.91MB
09/08/2010 22:31:39 max disk usage: 10.00GB
09/08/2010 22:31:39 (to change preferences, visit the web site of an attached project, or select Preferences in the Manager)
09/08/2010 22:31:39 Not using a proxy
09/08/2010 22:31:39 SETI@home Restarting task 20my10aa.13252.24885.11.10.119_0 using setiathome_enhanced version 603
09/08/2010 22:31:39 SETI@home Restarting task 22dc09ab.23792.13737.15.10.20_4 using setiathome_enhanced version 603
09/08/2010 22:31:39 SETI@home Restarting task 21dc09aa.399.48652.6.10.121_4 using setiathome_enhanced version 603
09/08/2010 22:31:39 SETI@home Restarting task 08my10ae.6880.63310.16.10.4_1 using setiathome_enhanced version 603
09/08/2010 22:31:52 SETI@home update requested by user
09/08/2010 22:31:56 SETI@home Sending scheduler request: Requested by user.
09/08/2010 22:31:56 SETI@home Requesting new tasks for GPU
09/08/2010 22:32:25 SETI@home Scheduler request completed: got 21 new tasks
09/08/2010 22:32:25 SETI@home Message from server: No work can be sent for the applications you have selected
09/08/2010 22:32:25 SETI@home Message from server: No work is available for Astropulse v5
09/08/2010 22:32:25 SETI@home Message from server: Your preferences allow work from applications other than those selected
09/08/2010 22:32:25 SETI@home Message from server: Sending work from other applications
09/08/2010 22:32:27 SETI@home Started download of 20my10ad.19272.17654.3.10.93
09/08/2010 22:32:27 SETI@home Started download of 20my10ad.19272.17654.3.10.113
09/08/2010 22:32:34 SETI@home Finished download of 20my10ad.19272.17654.3.10.113
09/08/2010 22:32:34 SETI@home Started download of 21my10aa.15797.15200.11.10.97
09/08/2010 22:32:34 SETI@home Starting 20my10ad.19272.17654.3.10.113_0
09/08/2010 22:32:34 SETI@home [error] Process creation failed:
09/08/2010 22:32:34 SETI@home [error] Process creation failed:
09/08/2010 22:32:35 SETI@home [error] Process creation failed:
09/08/2010 22:32:35 SETI@home [error] Process creation failed:
09/08/2010 22:32:35 SETI@home [error] Process creation failed:
09/08/2010 22:32:36 SETI@home Computation for task 20my10ad.19272.17654.3.10.113_0 finished
09/08/2010 22:32:36 SETI@home Output file 20my10ad.19272.17654.3.10.113_0_0 for task 20my10ad.19272.17654.3.10.113_0 absent
09/08/2010 22:32:44 SETI@home Finished download of 20my10ad.19272.17654.3.10.93
09/08/2010 22:32:44 SETI@home Started download of 20my10ac.14201.270938.13.10.107
09/08/2010 22:32:44 SETI@home Starting 20my10ad.19272.17654.3.10.93_1
09/08/2010 22:32:44 SETI@home [error] Process creation failed:
09/08/2010 22:32:44 SETI@home [error] Process creation failed:
09/08/2010 22:32:45 SETI@home [error] Process creation failed:
09/08/2010 22:32:45 SETI@home [error] Process creation failed:
09/08/2010 22:32:46 SETI@home [error] Process creation failed:
09/08/2010 22:32:47 SETI@home Computation for task 20my10ad.19272.17654.3.10.93_1 finished
09/08/2010 22:32:47 SETI@home Output file 20my10ad.19272.17654.3.10.93_1_0 for task 20my10ad.19272.17654.3.10.93_1 absent
09/08/2010 22:32:48 SETI@home Finished download of 21my10aa.15797.15200.11.10.97
09/08/2010 22:32:48 SETI@home Started download of 21my10aa.15797.15200.11.10.122
09/08/2010 22:32:48 SETI@home Starting 21my10aa.15797.15200.11.10.97_0
09/08/2010 22:32:48 SETI@home [error] Process creation failed:
09/08/2010 22:32:48 SETI@home [error] Process creation failed:
09/08/2010 22:32:49 SETI@home [error] Process creation failed:
09/08/2010 22:32:50 SETI@home [error] Process creation failed:
09/08/2010 22:32:51 SETI@home [error] Process creation failed:
09/08/2010 22:32:52 SETI@home Computation for task 21my10aa.15797.15200.11.10.97_0 finished
09/08/2010 22:32:52 SETI@home Output file 21my10aa.15797.15200.11.10.97_0_0 for task 21my10aa.15797.15200.11.10.97_0 absent
09/08/2010 22:32:56 Suspending network activity - user request

What im doing wrong?
32) Message boards : Number crunching : Pending credit: NOT WORKING (Message 1023673)
Posted 8 Aug 2010 by IFRS
Post:
Mine is not working now, like 90% of the time. Its very rare that it works. Nothing for months now.
33) Message boards : Number crunching : Closed *SETI/BOINC Milestones [ v2.0 ] - XXI* Closed (Message 1023548)
Posted 7 Aug 2010 by IFRS
Post:
Congratulations to all you folks, it´s nice to see things moving on.
Nice mark you hit Steve. 5 million is a lot of work.
My two 460 are arriving this week and I will jump to Fermi too. Not a big gun like the machine you own, but what I can afford right now...
45 million in here, still holding RAC #4, im happy :D
34) Message boards : Number crunching : Server Run, July 30 - August 2 2010 (Message 1022723)
Posted 5 Aug 2010 by IFRS
Post:
If your PC would have at least 4 (for example GTX260-216) GPUs, you would need to have at least ~ 700 normal WUs/day.
For the three day outage you need at least ~ 2,100 normal WUs.
For to have little bit security reserves (4 day WU cache) = ~ 2,800 WUs.

If you would let run the BOINC Manager alone and your PC get all the time 'no tasks available' and a backlog for the new work request.. It's not possible to fill up the WU cache with ~ 2,800 WUs.

If you get 1/4 shorties and 3/4 normal WUs you would need ~ 2,100 normal and ~ 2,800 shorty WUs = ~ 4,900 WUs for 4 days. BTW, and I don't think the BOINC Client/Manager can manage this big WU cache.

If the SETI@home scheduler send your BOINC ~ 20 WUs/request your BOINC need ~ 245 well contacts.

I think with this example it's well shown that only ~ 24 hours without or increased limit is too less.


Exactly. A 10k RAC machine, single CUDA, won´t need any babysit, or near that. But top 100 hosts, wich I guess are owned the most by the people that use this foruns, need a good amount of babysit, wich is doubled now on this system.
Some of them, like Sutaru say, can´t have enough work for the shortage. IF you can, BOINC can´t handle that much WU´s without hanging the machine, or even REPORT them when they are uploaded.
All I know is the big guns are suffering. Not complaining, just saying. If something can be done to avoid it, I think it should, because the hardcore users put big money and time on the project, for the science of it.
35) Message boards : Number crunching : Server Run, July 30 - August 2 2010 (Message 1022520)
Posted 4 Aug 2010 by IFRS
Post:
Not to mention that the babysit on big crunchers, that never was low, its like double now, and sometimes you can´t fill them enough for the outage = frustration. I don´t know how much time I will be able to keep with this pace before I got sick of it. Working on the machines like 3 or 4 hours everyday just to keep the farm running is a price that I may not be able to pay FOREVER.
36) Message boards : Number crunching : Server Run, July 30 - August 2 2010 (Message 1022068)
Posted 2 Aug 2010 by IFRS
Post:
It seems like they didn´t lift the limits on this monday, right?
My faster machine always wait for monday and isn´t get enough today :p

They did raise the limit, but didn't remove limit, look about 6 posts up :)


LOL true, sorry. Good enough on that limits :)
I guess the work is just not coming as it should then.
37) Message boards : Number crunching : Server Run, July 30 - August 2 2010 (Message 1022043)
Posted 2 Aug 2010 by IFRS
Post:
It seems like they didn´t lift the limits on this monday, right?
My faster machine always wait for monday and isn´t get enough today :p
38) Message boards : Number crunching : Running SETI@home on an nVidia Fermi GPU (Message 1021839)
Posted 2 Aug 2010 by IFRS
Post:
Thank you very much for your aid. I will let you know if all goes well when new hardware arrives. Old brave GTX 295 goes to my trusty Q9550 to make a nice 30k rig :D
39) Message boards : Number crunching : Running SETI@home on an nVidia Fermi GPU (Message 1021622)
Posted 1 Aug 2010 by IFRS
Post:

First, shut down BOINC completely and use Task Manager to be sure boinc.exe is no longer running. Then you can use the Lunatics installer and select only the appropriate AK_v8b CPU S@H Enhanced application plus the Astropulse CPU application. After the install finishes, add the Fermi information to app_info.xml. The needed files should still be in place, just check that every filename in the app_info.xml has a matching file. Then you can restart BOINC.
                                                                 Joe

Hi guys, there is a lot of very nice info on this post, but it is so much info that I may have lost something, mostly from language lack of skills :p
Im finally going for Fermi, with 2 GTX 460 ordered to replace my GTX 295 on one of my i7.
Basically, after installing the later BOINC and Nvidia drivers, what I have to do is what Josef say on this nice tip?
Ty all in advance!

I posted that for Rich-E, who had been running stock, including the 6.10 Fermi version. Your computers are hidden, but I guess from your RAC you are already running optimized and ought to look at other posts for advice.
                                                               Joe


Yes I am Josef. Im note sure what to do, but I guess I just need to add the Fermi information in the app_info.xml file and the proper files to my BOINC folder then?
40) Message boards : Number crunching : Running SETI@home on an nVidia Fermi GPU (Message 1021524)
Posted 1 Aug 2010 by IFRS
Post:
[/quote]
First, shut down BOINC completely and use Task Manager to be sure boinc.exe is no longer running. Then you can use the Lunatics installer and select only the appropriate AK_v8b CPU S@H Enhanced application plus the Astropulse CPU application. After the install finishes, add the Fermi information to app_info.xml. The needed files should still be in place, just check that every filename in the app_info.xml has a matching file. Then you can restart BOINC.
                                                                 Joe
[/quote]

Hi guys, there is a lot of very nice info on this post, but it is so much info that I may have lost something, mostly from language lack of skills :p
Im finally going for Fermi, with 2 GTX 460 ordered to replace my GTX 295 on one of my i7.
Basically, after installing the later BOINC and Nvidia drivers, what I have to do is what Josef say on this nice tip?
Ty all in advance!


Previous 20 · Next 20


 
©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.