Missing a Deadline
5 Mar 2005 10:27:07 UTC
Topic 188274
(moderation:
I've been running some more modern machines and just decided to try my old P2-333 with Win98SE running 24/7 with no screensaver. The "To Completion" estimate indicates aroud 9 days (215 hours) which will miss the deadline. What happens if a deadline is missed? Should I just forget this machine for E@H?
Missing a Deadline
)
BOINC is not supposed to download work if your computer will not be able to finish it in time. However one of the bug fixes for multi-project running broke this.
I would advise detaching that computer until the deadlines are either extended or enforced properly.
BOINC WIKI
BOINCing since 2002/12/8
> BOINC is not supposed to
)
> BOINC is not supposed to download work if your computer will not be able to
> finish it in time. However one of the bug fixes for multi-project running
> broke this.
The E@H scheduler will always allow a machine to download one WU, even if it can't complete it in time, provided that it does not have any queued or in-progress E@H work.
Bruce
Director, Einstein@Home
> > BOINC is not supposed to
)
> > BOINC is not supposed to download work if your computer will not be able
> to
> > finish it in time. However one of the bug fixes for multi-project
> running
> > broke this.
>
> The E@H scheduler will always allow a machine to download one WU, even if it
> can't complete it in time, provided that it does not have any queued or
> in-progress E@H work.
>
> Bruce
>
Would it be possible to modify the scheduler to not allow work if the machine could not get the work done if it ran E@H 100%? I know that there are complaints about not downloading work if the machine could finish the work if it was the only work on the computer, but this is a slightly different case.
It is still my belief that the client should look at all of the work it has on hand before requesting work from any project. It is my hope that the BOINC client will eventually get it the client side schedulers right.
BOINC WIKI
> > > BOINC is not supposed
)
> > > BOINC is not supposed to download work if your computer will not be
> able
> > to
> > > finish it in time. However one of the bug fixes for multi-project
> > running
> > > broke this.
> >
> > The E@H scheduler will always allow a machine to download one WU, even if
> it
> > can't complete it in time, provided that it does not have any queued or
> > in-progress E@H work.
> >
> > Bruce
> >
> Would it be possible to modify the scheduler to not allow work if the machine
> could not get the work done if it ran E@H 100%?
No, I can't do this.
Cheers,
Bruce
Director, Einstein@Home
Ive just detached a PII
)
Ive just detached a PII 300Mhz machine from this project because it was missing deadlines. Apparently its not fast enough - especially when dividing its time between E@H and S@H. I would hope that the deadlines could be extended to allow slower machines to participate. I know from experience with S@H that many users keep older machines around to crunch project data, and with the deadlines set the way they are for E@H, its kind of like you're saying you dont want older machines around. Thats unfortunate.
Just curios. A pII 300 should
)
Just curios. A pII 300 should do an Einstein WU in around 60H (2.5 days) running 24/7 with equal share with SETI the turnaround time would be 5 days. With the “Connect to network about every� set to 0.01 you would have almost a 2 day margin towards the deadline.
Then you're really interested in a subject, there is no way to avoid it. You have to read the Manual.
> Just curios. A pII 300
)
> Just curios. A pII 300 should do an Einstein WU in around 60H (2.5 days)
> running 24/7 with equal share with SETI the turnaround time would be 5 days.
> With the “Connect to network about every� set to 0.01 you would have
> almost a 2 day margin towards the deadline.
Thats a lot of criteria I have to meet.
I shouldnt have to use your favourite preferences to on my computers (eg: 0.01 days), I have mine set to contact every 2 days. Even so, this was not the problem as the work unit I was evaluating on this machine had not completed and was not waiting to report.
This is a screensaver application. I should have the option to process work only when the machine is idle (I actually do have it running 24/7, but I should still have the option).
BOINC initially estimated 45 hours to process the E@H work unit on this machine. I noticed yesterday, that I had less than 12 hours to complete about 20 hours worth of work. This may have been due to tweaking things like project share over the past few days, as I have only just started using BOINC and am in the process of tuning it to suit my particular environment so that it best fits the machines I have here.
There is no point having a range of perferences if they have to be set a certain way to satisfy a particular project. Remember that BOINC general preferences apply across all projects and all computers (Yuck). E@H is one of many projects I will be processing for (on both slow and fast machines, with diferent project mixes on each) and I will not set my general (all projects, all computers) preferences specifically for this one project.
The example you gave convinces me that it may be possible to process E@H work on this machine (shared 50/50 with S@H, as I had it set up) but I have opted to replace E@H on that machine with Predictor, as I can be assured of meeting their deadlines and getting credit for the work I have processed.
Other projects set reasonable deadlines for processing work, allowing for slower machines and multiple projects. Its a pitty that E@H doesnt. It certanly has the coolest looking screen saver.
> > Just curios. A pII 300
)
> > Just curios. A pII 300 should do an Einstein WU in around 60H (2.5 days)
> > running 24/7 with equal share with SETI the turnaround time would be 5
> days.
> > With the “Connect to network about every� set to 0.01 you would have
> > almost a 2 day margin towards the deadline.
>
> Thats a lot of criteria I have to meet.
>
> I shouldnt have to use your favourite preferences to on my computers
> (eg: 0.01 days), I have mine set to contact every 2 days. Even so, this was
> not the problem as the work unit I was evaluating on this machine had not
> completed and was not waiting to report.
>
> This is a screensaver application. I should have the option to process
> work only when the machine is idle (I actually do have it running 24/7, but I
> should still have the option).
>
> BOINC initially estimated 45 hours to process the E@H work unit on this
> machine. I noticed yesterday, that I had less than 12 hours to complete about
> 20 hours worth of work. This may have been due to tweaking things like
> project share over the past few days, as I have only just started using BOINC
> and am in the process of tuning it to suit my particular environment so that
> it best fits the machines I have here.
>
> There is no point having a range of perferences if they have to be set a
> certain way to satisfy a particular project. Remember that BOINC general
> preferences apply across all projects and all computers (Yuck). E@H is one of
> many projects I will be processing for (on both slow and fast machines, with
> diferent project mixes on each) and I will not set my general (all projects,
> all computers) preferences specifically for this one project.
>
> The example you gave convinces me that it may be possible to process E@H work
> on this machine (shared 50/50 with S@H, as I had it set up) but I have opted
> to replace E@H on that machine with Predictor, as I can be assured of meeting
> their deadlines and getting credit for the work I have processed.
>
> Other projects set reasonable deadlines for processing work, allowing for
> slower machines and multiple projects. Its a pitty that E@H doesnt. It
> certanly has the coolest looking screen saver.
>
There is a discussion about how to redesign the client side scheduler to cope with situations like this. I believe that it shoule be possible to run any set of configurations and not get into trouble. However, it would mean not always having a WU of a particular type on the client at any given time. E.g. if you had Einstein set to a resource share of .01 and S@H set to .99, then in order to crunch the work on time, the Einstein WU would have to get extra time (above its 1%) while it was on the machine, however, to compensate for this, there would be times (in this case much of the time) where there was no Einstein WU on the machine at all.
BOINC WIKI