Message boards : Number crunching : Choices are limited for target CPU run time selection
Author | Message |
---|---|
mikus Send message Joined: 7 Nov 05 Posts: 58 Credit: 700,115 RAC: 0 |
For several weeks I have been running with my 'target CPU run time' value at 10 hours. I wanted to increase that parameter SLIGHTLY. But today the webpage offers me the choice of setting that value to 10 hours, or to 16 hours -- NOTHING in between. Does the project not __trust__ us volunteer participants if instead we wished to set that value to, say, 12 hours ?? . |
David E K Volunteer moderator Project administrator Project developer Project scientist Send message Joined: 1 Jul 05 Posts: 1018 Credit: 4,334,829 RAC: 0 |
I just added more time options as requested. We are still waiting until recent bug fixes and work arounds for the 1% bug are tested on ralph before increasing the maximum to more than 1 day. |
Feet1st Send message Joined: 30 Dec 05 Posts: 1755 Credit: 4,690,520 RAC: 0 |
Wow! 10hrs to respond to a new user request! A new record perhaps! Regarding the time preferences, could you also have a look at Mikus' other post. Is there something to the pattern of the WUs that exceed the preference time? 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/ |
mikus Send message Joined: 7 Nov 05 Posts: 58 Credit: 700,115 RAC: 0 |
I just added more time options as requested. Thank you. I have now changed that parameter value to 12 hours. [I had seen occasional WUs take longer than the target specification. But given that the ideal scheduler should finish the WU *before* the target is reached, I felt that my target value deserved to be bumped up a little from where it was before.] . |
Message boards :
Number crunching :
Choices are limited for target CPU run time selection
©2024 University of Washington
https://www.bakerlab.org