Time to completition

sysfried
sysfried
Joined: 22 Jan 05
Posts: 11
Credit: 1107802
RAC: 0
Topic 187350

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.

venox7
venox7
Joined: 22 Jan 05
Posts: 16
Credit: 10072175
RAC: 0

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.

Sir Ulli
Sir Ulli
Joined: 18 Jan 05
Posts: 121
Credit: 104603
RAC: 0

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 ©

Bruce Allen
Bruce Allen
Moderator
Joined: 15 Oct 04
Posts: 1119
Credit: 172127663
RAC: 0

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

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.