Message boards : Number crunching : Best Current Target CPU Run Time?
Author | Message |
---|---|
The Gas Giant Send message Joined: 20 Sep 05 Posts: 23 Credit: 58,591 RAC: 0 |
With the short deadlines of CASP7 submissions what is the "best" target cpu run time for the project to complete work most effectively? I have just rejoined Rosetta on one of my hosts and want to do the "most" for the project with it. I currently have it set to 12hrs. Live long and crunch. PPaul (S@H1 8888) Do as I say, not as I do! |
Astro Send message Joined: 2 Oct 05 Posts: 987 Credit: 500,253 RAC: 0 |
Paul, Each Wu will crunch until the end of a model. I'm not sure how much gain can be had by increasing "run time". there might be some, but I don't think it's significant. I'm running 24 hours just "because". There's bound to be some loss in the starting/stopping of work, but I don't think that amounts to much. The biggest way to help is to increase resource share, or set other projects to NNW until the end of casp, etc. tony |
Feet1st Send message Joined: 30 Dec 05 Posts: 1755 Credit: 4,690,520 RAC: 0 |
There is no one right answer. Just make sure you select a WU runtime preference that allows you to report results before deadlines. I mean if you only use your PC 4 hours a day, then a 24hr WU probably is too long for you because it will take 6 days to crunch, which puts you too close to deadline. The current reccomendation from the project for the "typical user" is 8hr WU runtime. If you make change to your WU runtime preference, be sure you review the caution in the QA item on reducing modem time. This will help assure you don't get more work then you can crunch before the deadline. Add this signature to your EMail: Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might! https://boinc.bakerlab.org/rosetta/ |
Message boards :
Number crunching :
Best Current Target CPU Run Time?
©2024 University of Washington
https://www.bakerlab.org