Message boards :
Number crunching :
Queue on new machine
Message board moderation
Author | Message |
---|---|
Ghery S. Pettit Send message Joined: 7 Nov 99 Posts: 325 Credit: 28,109,066 RAC: 82 |
Interesting problem, probably has a simple solution (when you know the solution). I wound up with a new laptop in November when the old one lost its network connection (couldn't get an IP address - IT gave me a new box). Loaded BOINC and SETI on it and it runs fine. It now gets AP work units on occation, and they take 50-60 hours to run, but oh well. The problem is that it will not build up a large number of work units (regular SETI) in the queue. Right now there is an AP and a SETI Enhanced job running (dual core machine) and one SETI Enhanced work unit in reserve. And this is typical behavior for the machine. Everything else I have, with the same prefererences, has a number of days of work lined up. Even if I don't have an AP job running or in the queue, I still can't build up a reserve of work on this machine. As I said, any ideas? Thanks. |
Urs Echternacht Send message Joined: 15 May 99 Posts: 692 Credit: 135,197,781 RAC: 211 |
Could you copy and paste the first 100 lines (up to) from the messages tab of BOINC Managers advanced view after a restart of BOINC, please. That should help to find the right answer for you: My 1. guess -> Local preferences are used, but not configured for caching. _\|/_ U r s |
Ghery S. Pettit Send message Joined: 7 Nov 99 Posts: 325 Credit: 28,109,066 RAC: 82 |
1/8/2009 7:52:52 AM||Starting BOINC client version 6.4.5 for windows_intelx86 1/8/2009 7:52:52 AM||log flags: task, file_xfer, sched_ops 1/8/2009 7:52:52 AM||Libraries: libcurl/7.19.0 OpenSSL/0.9.8i zlib/1.2.3 1/8/2009 7:52:52 AM||Data directory: C:\Documents and Settings\All Users\Application Data\BOINC 1/8/2009 7:52:52 AM||Running under account gpettit 1/8/2009 7:52:54 AM||Processor: 2 GenuineIntel Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz [x86 Family 6 Model 15 Stepping 10] 1/8/2009 7:52:54 AM||Processor features: fpu tsc pae nx sse sse2 mmx 1/8/2009 7:52:54 AM||OS: Microsoft Windows XP: Professional x86 Editon, Service Pack 3, (05.01.2600.00) 1/8/2009 7:52:54 AM||Memory: 1.96 GB physical, 3.77 GB virtual 1/8/2009 7:52:54 AM||Disk: 74.53 GB total, 33.56 GB free 1/8/2009 7:52:54 AM||Local time is UTC -8 hours 1/8/2009 7:52:54 AM||Not using a proxy 1/8/2009 7:52:55 AM||No CUDA devices found 1/8/2009 7:52:55 AM||No coprocessors 1/8/2009 7:52:56 AM|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 4665107; location: work; project prefs: default 1/8/2009 7:52:56 AM||General prefs: from SETI@home (last modified 26-Dec-2008 23:24:31) 1/8/2009 7:52:56 AM||Computer location: work 1/8/2009 7:52:56 AM||General prefs: using separate prefs for work 1/8/2009 7:52:56 AM||Reading preferences override file 1/8/2009 7:52:56 AM||Preferences limit memory usage when active to 1003.62MB 1/8/2009 7:52:56 AM||Preferences limit memory usage when idle to 1806.51MB 1/8/2009 7:52:56 AM||Preferences limit disk usage to 10.00GB 1/8/2009 7:52:58 AM|SETI@home|Restarting task ap_01dc08ab_B2_P1_00004_20090107_28452.wu_1 using astropulse version 500 1/8/2009 7:53:00 AM|SETI@home|Restarting task 01no08ae.16894.4162.16.8.218_0 using setiathome_enhanced version 603 1/8/2009 7:54:57 AM||Using HTTP proxy proxy.dp.intel.com:911 1/8/2009 11:28:03 AM|SETI@home|Sending scheduler request: To fetch work. Requesting 39 seconds of work, reporting 0 completed tasks 1/8/2009 11:28:08 AM|SETI@home|Scheduler request completed: got 1 new tasks 1/8/2009 11:28:09 AM|SETI@home|Started download of 01no08ac.10186.2526.13.8.32 1/8/2009 11:28:13 AM|SETI@home|Finished download of 01no08ac.10186.2526.13.8.32 1/8/2009 11:33:28 AM|SETI@home|Computation for task 01no08ae.16894.4162.16.8.218_0 finished 1/8/2009 11:33:28 AM|SETI@home|Starting 01no08ae.16894.24612.16.8.62_1 1/8/2009 11:33:29 AM|SETI@home|Starting task 01no08ae.16894.24612.16.8.62_1 using setiathome_enhanced version 603 1/8/2009 11:33:30 AM|SETI@home|Started upload of 01no08ae.16894.4162.16.8.218_0_0 1/8/2009 11:33:35 AM|SETI@home|Finished upload of 01no08ae.16894.4162.16.8.218_0_0 1/8/2009 1:16:01 PM|SETI@home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 1 completed tasks 1/8/2009 1:16:06 PM|SETI@home|Scheduler request completed: got 0 new tasks 1/8/2009 3:11:51 PM|SETI@home|Sending scheduler request: To fetch work. Requesting 5 seconds of work, reporting 0 completed tasks 1/8/2009 3:12:01 PM|SETI@home|Scheduler request completed: got 1 new tasks 1/8/2009 3:12:03 PM|SETI@home|Started download of 20no08ad.31500.890.8.8.122 1/8/2009 3:12:42 PM|SETI@home|Finished download of 20no08ad.31500.890.8.8.122 1/8/2009 3:20:54 PM|SETI@home|Computation for task 01no08ae.16894.24612.16.8.62_1 finished 1/8/2009 3:20:54 PM|SETI@home|Starting 01no08ac.10186.2526.13.8.32_0 1/8/2009 3:20:54 PM|SETI@home|Starting task 01no08ac.10186.2526.13.8.32_0 using setiathome_enhanced version 603 1/8/2009 3:20:56 PM|SETI@home|Started upload of 01no08ae.16894.24612.16.8.62_1_0 1/8/2009 3:21:22 PM|SETI@home|Finished upload of 01no08ae.16894.24612.16.8.62_1_0 1/8/2009 3:46:04 PM|SETI@home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 1 completed tasks 1/8/2009 3:46:09 PM|SETI@home|Scheduler request completed: got 0 new tasks 1/8/2009 3:48:11 PM|SETI@home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 0 completed tasks 1/8/2009 3:48:16 PM|SETI@home|Scheduler request completed: got 0 new tasks 1/8/2009 3:48:16 PM||General prefs: from SETI@home (last modified 08-Jan-2009 15:47:55) 1/8/2009 3:48:16 PM||Computer location: work 1/8/2009 3:48:16 PM||General prefs: using separate prefs for work 1/8/2009 3:48:16 PM||Reading preferences override file 1/8/2009 3:48:16 PM||Preferences limit memory usage when active to 1003.62MB 1/8/2009 3:48:16 PM||Preferences limit memory usage when idle to 1806.51MB 1/8/2009 3:48:16 PM||Preferences limit disk usage to 10.00GB 1/8/2009 3:48:42 PM|SETI@home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 0 completed tasks 1/8/2009 3:49:02 PM|SETI@home|Scheduler request completed: got 0 new tasks 1/8/2009 4:15:39 PM|SETI@home|Sending scheduler request: To fetch work. Requesting 58 seconds of work, reporting 0 completed tasks 1/8/2009 4:15:44 PM|SETI@home|Scheduler request completed: got 1 new tasks 1/8/2009 4:15:46 PM|SETI@home|Started download of 01no08ad.15645.2117.16.8.112 1/8/2009 4:16:01 PM|SETI@home|Finished download of 01no08ad.15645.2117.16.8.112 And the settings for Work are the same as for Home, and the Home machines keep themselves well fed. |
Cosmic_Ocean Send message Joined: 23 Dec 00 Posts: 3027 Credit: 13,516,867 RAC: 13 |
Hm. That is kind of odd. The only thing I can think of is that the TDCF hasn't finished adjusting on that machine when APs hit it. If they come through frequently, it should sort itself out over time. I was just looking and you're not running into a quota issue, but I think that machine should have more than 4 "new" tasks. The important thing isn't so much of how much you have in the cache, as "is the CPU staying busy". Really as long as the CPU doesn't run out of work, that's all that matters. Linux laptop: record uptime: 1511d 20h 19m (ended due to the power brick giving-up) |
Urs Echternacht Send message Joined: 15 May 99 Posts: 692 Credit: 135,197,781 RAC: 211 |
1/8/2009 7:52:52 AM||Starting BOINC client version 6.4.5 for windows_intelx86 The red line in the quotation from your post tells you that your host is indeed using the "global_prefs_override.xml" -file. So, the preferences you have configured with the web gui have no more effect, as the local preferences setting from that file in your BOINC data directory are now used. But, if i understand your wishes correct, you want to use the preferences you set on the web. To do that open the option "Preferences..." in the "Advanced" menu of BOINC Managers advanced view and check if there is a button named "Clear". Hit it. That should clear your local preferences and your host should use the web settings again. If that button is missing: Simply find the named file on that host, stop the BOINC client, delete the file and restart BOINC. That should do it, too. _\|/_ U r s |
Ghery S. Pettit Send message Joined: 7 Nov 99 Posts: 325 Credit: 28,109,066 RAC: 82 |
Hm. That is kind of odd. The only thing I can think of is that the TDCF hasn't finished adjusting on that machine when APs hit it. If they come through frequently, it should sort itself out over time. I was just looking and you're not running into a quota issue, but I think that machine should have more than 4 "new" tasks. I would agree with that. The problem is that sometimes new work units are not forthcoming (like on Tuesdays) and it can (and has) run out of work. It's not my top cruncher, but it's not at the bottom of the list, either. |
Ghery S. Pettit Send message Joined: 7 Nov 99 Posts: 325 Credit: 28,109,066 RAC: 82 |
1/8/2009 7:52:52 AM||Starting BOINC client version 6.4.5 for windows_intelx86 THAT fixed it. Like blowing a dam. It's downloading new work like mad. THANKS! |
Urs Echternacht Send message Joined: 15 May 99 Posts: 692 Credit: 135,197,781 RAC: 211 |
Would have wondered if not. Happy crunching in 2009, when seti@home finishes its first decade. _\|/_ U r s |
Neil Blaikie Send message Joined: 17 May 99 Posts: 143 Credit: 6,652,341 RAC: 0 |
I know this may be the wrong thread for this question but it has been bugging. Is it better to leave "Allow new tasks" on or as I have a large cache 7 days an am running a fast dual core machine that crunches units quick, to set it to no new tasks. I run 6.4.5 but with an Optimized App and do not crunch AP units, it hasn't downloaded any at all. Any suggestions welcome. Thanks in advance. |
Mike Davis Send message Joined: 17 May 99 Posts: 240 Credit: 5,402,361 RAC: 0 |
I know this may be the wrong thread for this question but it has been bugging. Probably best to leave allow new tasks on... Personally, 7 days is a long cache to have. Mine is set to 2 days but 3 or 4 would probably suit you (allowing for a couple of days of possible down time. Dont know if you want to do astropulse, if you do, your appinfo file needs to reference astropulse in it and your account settings on here need to have it enabled (aswell as having the actual files on your puter). there are optimised apps for astropulse available. Please look in the 'New Optimized Apps Links -- READ ONLY THREAD' for combined packages for Optimised astropulse & multibeam for your computer |
Iona Send message Joined: 12 Jul 07 Posts: 790 Credit: 22,438,118 RAC: 0 |
I know this may be the wrong thread for this question but it has been bugging. I have a similar problem, with my latest (less ancient) PC and I have the cache set globally at 1 day. In its first day of operation, about 40 WUs were sent to it. As I did on the other Core 2 machine, I simply switch off "allow new work", then when I get to the last few WUs, switch it back on, then off again once the WUs have been downloaded. It sorts itslef out after a while..... Don't take life too seriously, as you'll never come out of it alive! |
©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.