Message boards : Number crunching : Why so long?
Author | Message |
---|---|
Stevie G Send message Joined: 15 Dec 18 Posts: 107 Credit: 832,067 RAC: 1,340 |
My computer is working on one Rosetta WU. Its elapsed time is 10: 31:09, with 67.362 completed and 04:59:47 remaining. Why should it take 16 hours to complete? Maybe it's because I do not have Virtual Box installed? This machine is too old and limited to run Virtual Box. Should I abort it? I don't want WUs that take so long. This is the first Rosetta WU I have seen in about a week. I might not get another one for another week. Task 1474736099 Name h3_3stub_D8.9_H_0001_PHE_complex_56_designed_1_0001_extract_A_SAVE_ALL_OUT_2910433_185_0 Workunit 1313773761 Created 23 Feb 2022, 5:46:50 UTC Sent 23 Feb 2022, 6:35:31 UTC Report deadline 26 Feb 2022, 6:35:31 UTC Received --- Server state In progress Outcome --- Client state New Exit status 0 (0x00000000) Computer ID 3551508 Run time CPU time Validate state Initial Credit 0.00 Device peak FLOPS 3.22 GFLOPS Application version Rosetta v4.20 windows_x86_64 Steven Gaber Oldsmar, FL |
Falconet Send message Joined: 9 Mar 09 Posts: 353 Credit: 1,227,479 RAC: 2,238 |
Steve G, If you haven't changed the runtime settings at the Rosetta@home preferences, that WU should run for 8 hours of CPU time. If there is an issue with it (a model that won't finish, etc), a feature called the "watchdog" will kick 10 CPU hours after the first 8 CPU hours. So, if that is the case, once that task has run for 18 hours of CPU time, the task will end. |
.clair. Send message Joined: 2 Jan 07 Posts: 274 Credit: 26,399,595 RAC: 0 |
Some do take a lot longer than they are supposed to , but . If it is a zombie task that gains no cpu time just elapsed time , it will time out in a few days after wasting days of time , |
Message boards :
Number crunching :
Why so long?
©2024 University of Washington
https://www.bakerlab.org