High Priority

Author	Message
kittyman Volunteer tester Send message Joined: 9 Jul 00 Posts: 50494 Credit: 1,018,363,574 RAC: 2,276	Message 1275188 - Posted: 25 Aug 2012, 4:46:03 UTC - in response to Message 1275141. I only download tasks when I think I need them. how do you do it? Not to speak for the OP, but it's quite easy. You just go to the projects tab in Boinc and set the Seti project to 'no new tasks'. Then, when you want to request more (no guarantee you will get some, depending on the state of the servers) you set it back to 'allow new tasks'. "Learn from yesterday. Live for today. Hope for tomorrow." Albert Einstein "With cats." kittyman ID: 1275188 ·

Zapiao Volunteer tester Send message Joined: 29 Oct 01 Posts: 110 Credit: 122,278 RAC: 0	Message 1275141 - Posted: 25 Aug 2012, 3:29:40 UTC - in response to Message 1268534. Last modified: 25 Aug 2012, 3:33:44 UTC I only download tasks when I think I need them. how do you do it? ID: 1275141 ·

bill Send message Joined: 16 Jun 99 Posts: 861 Credit: 29,352,955 RAC: 0	Message 1268603 - Posted: 7 Aug 2012, 3:45:12 UTC A further observation with 2 days set as a buffer, if I download work units that are dead lined in 3 days any number of work units that come to more than 24 hours of work will start to run in high priority mode. ID: 1268603 ·

bill Send message Joined: 16 Jun 99 Posts: 861 Credit: 29,352,955 RAC: 0	Message 1268535 - Posted: 6 Aug 2012, 22:09:23 UTC - in response to Message 1268530. I dont think its related to Boinc 7. I got 40 days recently with 6.22 and settings of 2 and 3 days. DCF 1.3 I upgraded from 6.10.60. Maybe the strangeness started occurring after that release. ID: 1268535 ·

bill Send message Joined: 16 Jun 99 Posts: 861 Credit: 29,352,955 RAC: 0	Message 1268534 - Posted: 6 Aug 2012, 22:07:01 UTC - in response to Message 1268529. Luckily I've been running no new tasks because of all the strangeness since 7.x.x came out. I only download tasks when I think I need them. I don't trust the BOINC Manager any more. ID: 1268534 ·

Mike Volunteer tester Send message Joined: 17 Feb 01 Posts: 32172 Credit: 79,922,639 RAC: 181	Message 1268530 - Posted: 6 Aug 2012, 21:30:01 UTC I dont think its related to Boinc 7. I got 40 days recently with 6.22 and settings of 2 and 3 days. DCF 1.3 With each crime and every kindness we birth our future. ID: 1268530 ·

Jord Volunteer tester Send message Joined: 9 Jun 99 Posts: 15157 Credit: 4,362,181 RAC: 6	Message 1268529 - Posted: 6 Aug 2012, 21:24:49 UTC - in response to Message 1268522. Last modified: 6 Aug 2012, 21:26:48 UTC Lucky you didn't have a work request... I just tested mine with 10,000 days... 06/08/2012 23:17:29 \| SETI@home \| Requesting new tasks for CPU 06/08/2012 23:17:29 \| SETI@home \| [sched_op] CPU work request: 2591715913.38 seconds; 0.00 devices 06/08/2012 23:17:32 \| SETI@home \| Scheduler request completed: got 20 new tasks 06/08/2012 23:17:32 \| SETI@home \| [sched_op] estimated total CPU task duration: 161820 seconds ... and quickly suspended network after this, so I could bring minimum back down to 1 day without it downloading all work that Seti has on server at this time... :P 2591715913 seconds comes out as 29,996 days. About 10K days per Seti available CPU core. :) (I reported the bug to BOINC Alpha) ID: 1268529 ·

bill Send message Joined: 16 Jun 99 Posts: 861 Credit: 29,352,955 RAC: 0	Message 1268522 - Posted: 6 Aug 2012, 20:53:42 UTC 7.0.31 Noticed work units had shifted into high priority mode for some reason. After looking around I found that my local computing preferences had set themselves to minimum work buffer of 100 days. Setting the work buffer down to something reasonable the high priority went away. Strangeness. ID: 1268522 ·

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