Rising time to completion

Author	Message
DeMus Send message Joined: 2 Jan 09 Posts: 10 Credit: 55,278 RAC: 0	Message 58376 - Posted: 2 Jan 2009, 19:22:42 UTC Hi, I just started Rosetta and the first thing I noticed is the fairly long time it takes to finish a work unit. But, that's not all. I am used to smaller WU's with Seti@Home. I now see that the time to completion is not decreasing but increasing. Units start with 3.30.00 h and now, after having done 5%, the time to completion has gone up to 5 h. Can somebody please explain that to me? I run Ubuntu Linux 8.04 and rosetta_beta_5.98_x86_64-pc-linux-gnu crunching program. ______ DeMus ID: 58376 · Rating: 0 · rate: / Reply Quote

Mod.Sense Volunteer moderator Send message Joined: 22 Aug 06 Posts: 4018 Credit: 0 RAC: 0	Message 58381 - Posted: 2 Jan 2009, 20:05:01 UTC Jan, Rosetta actually allows you to configure the target runtime you would prefer. This is done in the Rosetta preferences on the website (not the general preferences). It is a target, not an absolute. When you first get started, the default is currently a 3 hours runtime target. And BOINC's benchmarks and etc. are used to get an initial guess at the runtime. Yours was 3.5 hours. But if you've set your target higher, then this will be what actually gets used. BOINC will then, in retrospect, see the actual runtime and use that in future estimates of runtime. You may have set your target higher then the 3 hours, and so Rosetta knows it is likely to run longer, but BOINC has to "see" it happen. It will settle down once you complete a few tasks. Rosetta Moderator: Mod.Sense ID: 58381 · Rating: 0 · rate: / Reply Quote

DeMus Send message Joined: 2 Jan 09 Posts: 10 Credit: 55,278 RAC: 0	Message 58387 - Posted: 2 Jan 2009, 21:28:08 UTC - in response to Message 58381. Jan, Rosetta actually allows you to configure the target runtime you would prefer. This is done in the Rosetta preferences on the website (not the general preferences). It is a target, not an absolute. When you first get started, the default is currently a 3 hours runtime target. And BOINC's benchmarks and etc. are used to get an initial guess at the runtime. Yours was 3.5 hours. But if you've set your target higher, then this will be what actually gets used. BOINC will then, in retrospect, see the actual runtime and use that in future estimates of runtime. You may have set your target higher then the 3 hours, and so Rosetta knows it is likely to run longer, but BOINC has to "see" it happen. It will settle down once you complete a few tasks. Thank you for the explanation. I guess I just have to wait a while to see things stabilize. ______ DeMus ID: 58387 · Rating: 0 · rate: / Reply Quote