Message boards : Number crunching : Newbie Question? Time To Complete WUs?
Author | Message |
---|---|
Rifleman Send message Joined: 19 Nov 08 Posts: 17 Credit: 139,408 RAC: 0 |
HI. I ust started running Rosetta. After running all night I noticed 2 tasks has stalled and errors forced me to abort. The new tasks have been running 2 hours with 15 hours to go. Is that normal? Are my settings ok for this PC? I don't mind the long times but if I can speed things up so much the better. Thanks for any advice. |
![]() ![]() Send message Joined: 30 May 06 Posts: 5694 Credit: 5,883,085 RAC: 2,068 ![]() |
HI. I ust started running Rosetta. After running all night I noticed 2 tasks has stalled and errors forced me to abort. just a few things, let the tasks run until they either stall for a hour and are not being blocked by any other DC project. time remaining will change as boinc manager learns your system better. the time remaining will also kind of stick as the task gets closer to the end. nothing to worry about. also have a look at your preferences settings by clicking on the your preferences button on the boinc manager. you can check you run time preferences by looking at the rosetta at home preferences area. also check the settings in computing preferences. if your run time is greater than 6 hrs run time, bring it back down to that. This offers the best results for the rosetta team. use all 4 cores if you want for rosetta, just make sure your account is configured for that on the multi processors line in the computing preferences section. |
Mod.Sense Volunteer moderator Send message Joined: 22 Aug 06 Posts: 4018 Credit: 0 RAC: 0 |
Rob the default runtime is 3 hours. Any given task can vary, but in general, you've not described anything unusual here... other then the errors that you feel warranted aborting the tasks. ...I see now in looking at your task list that these ran for 18 hours. Rosetta has a "watchdog" that looks for tasks that are running too long. It bases it's decision upon the runtime you have configured in your Rosetta preferences. Generally it waits for 3 times the desired runtime before aborting it for you. And, unless you changed it, the runtime defaults to 3hrs, so I would have expected the watchdog to end them for you after about 9 hours. Obviously it didn't, so either one of my assumptions about your settings is incorrect, or the watchdog was unsuccessful at ending the task. Your successful task ran for over 17 hours and generated 21 models. At the end of each model is when the runtime preference is checked and the task decides if it should run another model, or report the result. So, assuming all of those 21 models ran for about the same amount of time, your runtime preference must not be set to the 3hr default. Go to the participants link at the top of this msg board and select the Rosetta preferences to check how you have the runtime set. Rosetta Moderator: Mod.Sense |
Rifleman Send message Joined: 19 Nov 08 Posts: 17 Credit: 139,408 RAC: 0 |
Thanks for the replies and info guys. I DID play with the preferences so if the long time to complete the tasks are normal--I'll leave it alone. I have 3 rosetta crunching and trying to finish a SETI astropulse task-----which is going to take 80 hours or so. 31 hours in and 56 to go. I am not too impressed with this Phenom 9500. I should have gone with the Q6600 but it does what I need it to. |
Message boards :
Number crunching :
Newbie Question? Time To Complete WUs?
©2025 University of Washington
https://www.bakerlab.org