Why 23+ hour work units?

Questions and Answers : Wish list : Why 23+ hour work units?

To post messages, you must log in.

AuthorMessage
Aron Sebastian

Send message
Joined: 17 Jul 08
Posts: 1
Credit: 35,451
RAC: 0
Message 55077 - Posted: 14 Aug 2008, 3:30:09 UTC
Last modified: 14 Aug 2008, 3:32:01 UTC

I also run seti@home & 5 projects on World Community Grid. Why can't Rosetta@home cut the length/time it takes to crunch 23+ hour work units? It makes it difficult to meet deadlines for other projects unless I manually hit "no new tasks" & suspend other projects in order to crunch Rosetta, then suspend Rosetta in order to crunch Seti (which never has tasks longer than 4 hours) & World Community Grid, which never has tasks longer than 7 hours. I'm running Vista Ulltimate on a dual core 3000+ GHz system w/8 Gig of RAM & have no problem crunching the work units, but only if I watch BOINC like a hawk & control what runs when.

Rosetta@home needs to even up the playing field. I believe that people with older hardware are scared off Rosetta@home when they see how long an average workunit is. And users who run more that one project may begin to think twice about participating in Rosetta@home with the consistently huge work units.

For example, I can run 7 Seti@home work units in the same time it takes to complete 1 Rosetta@home unit. And I can run an average of 5 World Community Grid projects in the same time as it takes to run one Rosetta unit.

Since I crunch 2 work units at a time, it comes out to 2 Rosetta units for 14 Seti units or 10 World Community Grid units.
ID: 55077 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Nothing But Idle Time

Send message
Joined: 28 Sep 05
Posts: 209
Credit: 139,545
RAC: 0
Message 55080 - Posted: 14 Aug 2008, 6:22:42 UTC - in response to Message 55077.  

... Why can't Rosetta@home cut the length/time it takes to crunch 23+ hour work units?

Is your task runtime preference set to 24 hours? The output from one of your finished tasks shows that your runtime preference is 86,400 seconds:

<core_client_version>6.3.6</core_client_version>
<![CDATA[
<stderr_txt>
# cpu_run_time_pref: 86400
# random seed: 2347443
# cpu_run_time_pref: 86400
# cpu_run_time_pref: 86400
# cpu_run_time_pref: 86400
======================================================
DONE :: 1 starting structures 84962.5 cpu seconds
This process generated 44 decoys from 44 attempts
0 starting pdbs were skipped
======================================================


BOINC :: Watchdog shutting down...
BOINC :: BOINC support services shutting down...

</stderr_txt>
]]>

Change your computer's runtime preference to something lower. I believe you can choose from 1 hour to 24 hours


ID: 55080 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Mod.Sense
Volunteer moderator

Send message
Joined: 22 Aug 06
Posts: 4018
Credit: 0
RAC: 0
Message 55081 - Posted: 14 Aug 2008, 12:18:57 UTC

Aron, you can change your runtime preference on the website here. Click the link above this forum page labeled "[Participants]", once you have signed on, then you can change your Rosetta preferences there. Select a runtime that works for you. Just keep in mind it is a "preference" not a "directive". The Rosetta client will do what it can to comply.

The default is to shoot for a 3 hour runtime. Some tasks will take longer then that, especially on older machines, but most can complete that required first model in the 3 hours. Some tasks will complete is less time then that. This because to start another model would take you past your preference. And so they are ended a little early.
Rosetta Moderator: Mod.Sense
ID: 55081 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote

Questions and Answers : Wish list : Why 23+ hour work units?



©2024 University of Washington
https://www.bakerlab.org