Posts by Fred G
|
1)
Message boards :
Number crunching :
Welcome to the 13 year club
(Message 1235289)
Posted 23 May 2012 by  Fred G
Post: I'm still crunching although my farm had dwindled down to one full time cruncher. Still trying to do my part... |
|
2)
Message boards :
Number crunching :
4 core only crunching 1 wu now
(Message 1176267)
Posted 7 Dec 2011 by Fred G
Post: I upgraded to 0.39 and it still only downloads cuda wu's. BOINC rescheduler won't work running on a schedule. It fails to shut down BONIC. I'm going to let it run all my work then uninstall clean, the system then reinstall fresh. |
|
3)
Message boards :
Number crunching :
4 core only crunching 1 wu now
(Message 1175947)
Posted 5 Dec 2011 by Fred G
Post: Once I crunch my on hand wu's I'll upgrade to 0.39. Thanks for all the help everyone! |
|
4)
Message boards :
Number crunching :
4 core only crunching 1 wu now
(Message 1175796)
Posted 5 Dec 2011 by Fred G
Post: consider running the BOINC rescheduler. It is a fairly simple tool to move WU's from CPU to GPU over visa versa. THANK YOU!! It worked. It changed about half of my wu's back to CPU. I'm still interested in finding out why it started downloading just GPU work. EDIT: When I found the problem I set it to No new task. Once I started it back to receiving task it only requested GPU task? I'm wondering if there's something in app_info that has changed... 12/5/2011 1:52:35 AM | SETI@home | work fetch resumed by user 12/5/2011 1:52:39 AM | SETI@home | Sending scheduler request: To fetch work. 12/5/2011 1:52:39 AM | SETI@home | Requesting new tasks for NVIDIA GPU 12/5/2011 1:52:48 AM | SETI@home | Scheduler request completed: got 22 new tasks <app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b_win_x64_SSE3.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_SSE3.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_SSE3.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_x38g_win32_cuda32.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_32_16.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_32_16.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_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>Lunatics_x38g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.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>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x38g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.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>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>Lunatics_x38g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.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>Lunatics_x38g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.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>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x38g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.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>Lunatics_x38g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
</app_version>
</app_info>
|
|
5)
Message boards :
Number crunching :
4 core only crunching 1 wu now
(Message 1175742)
Posted 5 Dec 2011 by Fred G
Post: Checking your allocated units, I do not see any CPU units. They are all for the GPU. You are correct! I can't figure out why I just received GPU units. There's 419 in my cache and I'll never complete them before the expire running one at a time. Well, you won't have been running BOINC v6.12.34 since 2008, that's for sure (it was only released at the end of July 2011). My Q6600 has been running crunching since 2008 not v6.12.34.:) I upgraded in August I believe so it's been working great until now.... |
|
6)
Message boards :
Number crunching :
4 core only crunching 1 wu now
(Message 1175380)
Posted 3 Dec 2011 by Fred G
Post: I have a Q6600 system that has been in operation since 2008. I just noticed it stopped crunching 4 wu's a couple days ago and is now only running 1 wu plus one cuda wu. I checked the preferences and nothing has changed. I'm running Lunatics Unified Installer v0.38 bonic ver 6.12.34 Any ideas how to correct this? This one has stumped me... http://setiathome.berkeley.edu/show_host_detail.php?hostid=4632075 |
|
7)
Message boards :
Number crunching :
Welcome to the 11 year club
(Message 1050325)
Posted 22 Nov 2010 by Fred G
Post: Me too! |
|
8)
Message boards :
Number crunching :
I'm quitting Seti 'cause of increased power cost coming from "Cap and Trade"
(Message 912244)
Posted 28 Jun 2009 by Fred G
Post: RottenMutt, I know how you feel. Since AP ran out I've been shutting down my farm. All but two are now getting a deserved rest. I've been crunching for 10 years and never thought I'd ever shut down. The direction our country is heading that little extra money might come in handy sooner than later. |
|
9)
Message boards :
Number crunching :
Welcome to the 10 year club
(Message 906450)
Posted 12 Jun 2009 by Fred G
Post: I hit my 10 year mark last month. Time sure goes by fast! |
|
10)
Message boards :
Number crunching :
Still Crunching Away - 10 Years Later!
(Message 897654)
Posted 21 May 2009 by Fred G
Post: Wow, I missed my 10 year also. I'm just 57 but I do have a hard time keeping my RAC up! ;) |
|
11)
Message boards :
Number crunching :
BOINC, Ver 6.4.5, is ignoring "Additional work buffer"
(Message 854049)
Posted 16 Jan 2009 by Fred G
Post: Something was definitely wrong with the date. In the Statistics tab it had Jun 09 then Dec 10 then Mar 11 and so on. I completely uninstalled it and reinstalled and it's starting to fill the cache now. |
|
12)
Message boards :
Number crunching :
BOINC, Ver 6.4.5, is ignoring "Additional work buffer"
(Message 854018)
Posted 16 Jan 2009 by Fred G
Post: I've checked the system time and I know that I didn't change it and back again. I've also compared CLIENT_STATE.XML to another computer and there is no discernible difference in times. I think I'll uninstall and reinstall it and see if that will help. |
|
13)
Message boards :
Number crunching :
BOINC, Ver 6.4.5, is ignoring "Additional work buffer"
(Message 853974)
Posted 15 Jan 2009 by Fred G
Post: I understand how High Priority works, however it should work when WU's are in danger of exceeding the deadline not just kick in and empty the cache. None of my WU's were close to going over the deadline but it emptied it anyway. I've been doing this for a while and I've had things happen that created client errors and dumped all my cache but it built back up fairly quickly after it started reporting good WU's. No such thing this time. |
|
14)
Message boards :
Number crunching :
BOINC, Ver 6.4.5, is ignoring "Additional work buffer"
(Message 853858)
Posted 15 Jan 2009 by Fred G
Post: I have the same problem with this computer. http://setiweb.ssl.berkeley.edu/show_host_detail.php?hostid=3508634 It was running fine then started running all WU's in high priority even though it was working on WU's due in two weeks and completed them in one day. I've updated Bonic an it still will only give me WU's one for one but it did stop it running in high priority. I've tried everything I can think of but it still only will download a WU just before one finished or has been uploaded. The Tasks shows no problems all are good. You are right. % of time BOINC client is running 100 % While BOINC running, % of time work is allowed 0.005 % Average CPU efficiency 0.909987 Task duration correction factor 0.137391 I don't know what happened but I haven't had any down time with the computer and haven't reported any bad WU's. A few days ago I noticed it running in High Priority and had a full cache. But the problem is it's not refilling the cache. |
|
15)
Message boards :
Number crunching :
BOINC, Ver 6.4.5, is ignoring "Additional work buffer"
(Message 853855)
Posted 15 Jan 2009 by Fred G
Post: Why do you think it's not? It started running all WU's in High Priority without a need to and stopped downloading the cache. Tuesday updates will cause this computer to be idle since I won't have any WU's to run.I have the same problem with this computer. http://setiweb.ssl.berkeley.edu/show_host_detail.php?hostid=3508634 It was running fine then started running all WU's in high priority even though it was working on WU's due in two weeks and completed them in one day. I've updated Bonic an it still will only give me WU's one for one but it did stop it running in high priority. I've tried everything I can think of but it still only will download a WU just before one finished or has been uploaded. The Tasks shows no problems all are good. |
|
16)
Message boards :
Number crunching :
BOINC, Ver 6.4.5, is ignoring "Additional work buffer"
(Message 853845)
Posted 15 Jan 2009 by Fred G
Post: I have the same problem with this computer. http://setiweb.ssl.berkeley.edu/show_host_detail.php?hostid=3508634 It was running fine then started running all WU's in high priority even though it was working on WU's due in two weeks and completed them in one day. I've updated Bonic an it still will only give me WU's one for one but it did stop it running in high priority. I've tried everything I can think of but it still only will download a WU just before one finished or has been uploaded. The Tasks shows no problems all are good. |
|
17)
Message boards :
Number crunching :
Client error question
(Message 825202)
Posted 31 Oct 2008 by Fred G
Post: Thanks for the info. I thought it wouldn't work but wanted to make sure. I got the problem fixed. It's just one of those things when setting up a new OC'd computer. I just wanted to try and recover some of my bad uploads. I've never had it take over 24 hours to start sending me new WU's and thought if I could get some to report as good it would start sending me some more. Right now I have it crunching the backup with the network activity suspended just to make sure I have it stabilized. |
|
18)
Message boards :
Number crunching :
Client error question
(Message 825178)
Posted 31 Oct 2008 by Fred G
Post: I'm setting up a new computer and had problems with my DDR2 ram which caused my WU's to be reported as client errors. I've waited about 24 hours without and new WU's being downloaded, exceeded quota. I have a backup of my WU's but I'm not sure how many have been reported correctly. My question is if I use my backup will it cause any problems with some being reported good twice and will it cause any problems reporting some good after being reported as client errors? |
|
19)
Message boards :
Number crunching :
Pending Credit Setting for Long Time?
(Message 653259)
Posted 3 Oct 2007 by Fred G
Post: I know that my pending credit has really grown over the last 3 or 4 months. I'm up to about 20,000 credits pending. I've never seen it that high. 3,000 was about the highest I would carry. |
|
20)
Message boards :
Number crunching :
Pending Credit.
(Message 634618)
Posted 6 Sep 2007 by Fred G
Post: All I know is mine has been climbing constantly for a few weeks. I'm up to now...Pending credit: 19,089.07 |
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.