Time to completition
25 Jan 2005 22:00:08 UTC
Topic 187350
(moderation:
Hi there.
Running Boinc 4.16 (just upgraded to 4.18 2 min ago) I noticed that the calculated time to completition is way off the real time it takes to finish the results... maybe the E@H Team wants to change that?
AMD64 CPU calculated: 6:34 h
actual time 8+ h
Intel P4 3.2 GHz Prescott based calculated: 7+ h
actual time 10+ h
just a thought.
Time to completition
)
> AMD64 CPU calculated: 6:34 h
> actual time 8+ h
>
> Intel P4 3.2 GHz Prescott based calculated: 7+ h
> actual time 10+ h
>
Got similar time differences.
my Athlon64 3.200+
)
my Athlon64 3.200+
Picture about 250 KB
running SAH and EAH at 50:50
Greetings from Germany NRW
Ulli S@h Berkeley's Staff Friends Club m7 ©
We've just found and fixed a
)
We've just found and fixed a bug where a job that was stopped in the second half then restarted might show a percentage complete which is less than 50% for some time. This is because the restarted job resumes part of the 'first half' computation from the last saved checkpoint before going back to resuming the second half of the computation from a saved checkpoint. How large this effect is on any given machine depends upon how the user preferences have been set for checkpointing frequency / interval.
This will be fixed in our next app release.
Cheers,
Bruce
Director, Einstein@Home