Report deadline is too short
23 Apr 2005 20:10:20 UTC
Topic 189024
(moderation:
The report deadline is way too short, I often hit the problem that when a WU starts crunching it is already too late to meet the deadline, ofcourse BOINC doesn't see this problem until it is only a few hours left and then warns about a deadline problem...
My suggestion is to add atleast 1 day to the deadline thus allowing machines in the 330-500 MHz range to participate without risking to "pass the line", as it is now it usually misses it with about 3-5 hours...
Regards / Chi
Report deadline is too short
)
Dump the pathetically slow Celeron.
*I still know CRAP when I see it.
> Dump the pathetically slow
)
> Dump the pathetically slow Celeron.
>
Why should I? It does the job even if it takes a little longer time...
Adjust your connect to date
)
Adjust your connect to date to a lower number, detach from other projects, thus freeing resources for Einstein to use.....Oh! take the Celeron out back and put it out of it's misery
Link to Unofficial Wiki for BOINC, by Paul and Friends
> > Dump the pathetically
)
> > Dump the pathetically slow Celeron.
> >
>
> Why should I? It does the job even if it takes a little longer time...
>
That's just it. It's not doing the job.
*I still know CRAP when I see it.
You guys are missing his
)
You guys are missing his point - irregardless of celeron or not.
I'm running a P4 2.4GZ with 512MB - not an old dog by any measure. However, I frequently don't finish them "on time" because the check in time is too brief. SETI@Home gives what, 2 weeks to return results? Considering folks may not run their PC for a couple of days when they are out of town, the 1 week window E@Home uses it too short.
They'd get more results from me if they bumped it out to two weeks.
'nuf said.
The client side CPU and
)
The client side CPU and download schedulers are being re-worked slightly to take deadlines more seriously. There are two modes for the new CPU scheduler, the normal mode that works like the one we have now, and the panic mode scheduler that crunches on the earliest deadline WU in an attempt to make it in on time (or make it less late). The download scheduler will prevent downloading from any project if it is determined that there is already too much work for the CPU scheduler to handle comfortably.
This code is still in development although it looks very promissing.
BOINC WIKI
> The client side CPU and
)
> The client side CPU and download schedulers are being re-worked slightly to
> take deadlines more seriously. There are two modes for the new CPU scheduler,
> the normal mode that works like the one we have now, and the panic mode
> scheduler that crunches on the earliest deadline WU in an attempt to make it
> in on time (or make it less late). The download scheduler will prevent
> downloading from any project if it is determined that there is already too
> much work for the CPU scheduler to handle comfortably.
>
> This code is still in development although it looks very promissing.
>
I like this change, that will hopefully stop all the fat que types from loading up on more WUWOUs than they can process.
Link to Unofficial Wiki for BOINC, by Paul and Friends
> Dump the pathetically slow
)
> Dump the pathetically slow Celeron.
>
>
I don't think there's any call for talk like that. Obviously Chiana is interested in putting the ol' machine to constructive use and that's admirable. Chiana, do you crunch for SETI or any other projects for which the Celeron might be better suited? Perhaps dedicate that machine solely to the project(s) with longer deadlines and shorter processing time. I keep my Celeron here on Einstein because it crunches a unit pretty quick, but my old K6-2 will definitely be doing SETI work only.
Happy Crunching ;)
Dig
> > Dump the pathetically
)
> > Dump the pathetically slow Celeron.
> >
> >
>
> I don't think there's any call for talk like that. Obviously Chiana is
> interested in putting the ol' machine to constructive use and that's
> admirable. Chiana, do you crunch for SETI or any other projects for which the
> Celeron might be better suited? Perhaps dedicate that machine solely to the
> project(s) with longer deadlines and shorter processing time. I keep my
> Celeron here on Einstein because it crunches a unit pretty quick, but my old
> K6-2 will definitely be doing SETI work only.
>
> Happy Crunching ;)
>
> Dig
>
Sorry for my PMS outburst. I should have just said what you did. If your machine can't do the job then please assign it to a project where it will be able to do the job. I just see too many people bitch about the 7 day return time being too short. I have just 1 machine attached to 4 projects and with a little bit of common sense it has no problem with any of the projects and my connect time is set to 1 day. What am I doing wrong???
Just a dumb broad,
Dominique
*I still know CRAP when I see it.
RapidEye says: > They'd get
)
RapidEye says:
> They'd get more results from me if they bumped it out to two weeks.
I agree with you. At least two weeks are needed to the report deadline.
# BTW, my Celeron 433MHz (Mendocino) machine produce one result per 3 days.
# I'm happy that no deadline problem is on this machine :) .
-- Zansei