Hello, BOINC developers.
I like this *plain fact statement*... "Running, to meet deadline"
I would only make very little change...:
"Running *now*, to meet deadline"
*Namaste*
Filip
2014-10-04 17:57 GMT+02:00 McLeod, John <[email protected]>:
> BOINC may be running tasks out of round robin order, but it is not
> panicking. Panic has the connotation of inconsidered fright. That is not
> what BOINC is doing. BOINC is considering the situa t ion and making a
> decision based on the best available knowledge. This is not panicking.
>
> Sent from my Android phone using TouchDown (www.nitrodesk.com)
>
> -----Original Message-----
> From: Erik Veit [[email protected]]
> Received: Saturday, 04 Oct 2014, 11:38AM
> To: McLeod, John [[email protected]]
> CC: [email protected] [[email protected]]
> Subject: Re: [boinc_dev] High priority status message removed.
>
> But that’s exactly what BOINC *is* doing. It’s stopped thinking, and is
> no longer considering all the normal scheduling rules. It’s scheduling on
> pure fear (panic) of a missed deadline.
>
>
> > On Oct 4, 2014, at 8:04 AM, McLeod, John <[email protected]> wrote:
> >
> > Panic is a word that we really do not want to use. When you panic, you
> stop thinking...
> >
> > Sent from my Android phone using TouchDown (www.nitrodesk.com<
> http://www.nitrodesk.com>)
> >
> > -----Original Message-----
> > From: Erik Veit [[email protected]]
> > Received: Saturday, 04 Oct 2014, 10:26AM
> > To: [email protected] [[email protected]]
> > Subject: Re: [boinc_dev] High priority status message removed.
> >
> >> Set a two day queue, and BOINC panics.
> >
> > Use the words that the users are already using.
> >
> > “Panic Mode”. It’s concise, easily understandable, no confusion with
> system priority, and is the term BOINC users have been using for years to
> describe it on all the forums.
> >
> >
> >
> >
> >> On Oct 4, 2014, at 5:48 AM, Richard Haselgrove <
> [email protected]> wrote:
> >>
> >> Just observe. I'm currently running two SIMAP tasks which were issued
> with a two-day deadline (additional replications required for validation -
> they must be using
> >>
> >> <reliable_reduced_delay_bound>X</reliable_reduced_delay_bound>
> >> When a need-reliable result is sent to a reliable host, multiply the
> delay bound by reliable_reduced_delay_bound (typically 0.5 or so).
> >>
> >> Set a two day queue, and BOINC panics.
> >>
> >> Don't judge every BOINC operation by the relaxed timings used at SETI.
> >>
> >>
> >>> ________________________________
> >>> From: Charles Elliott <[email protected]>
> >>> To: "'McLeod, John'" <[email protected]>; [email protected];
> [email protected]; [email protected]
> >>> Sent: Saturday, October 4, 2014 1:37 PM
> >>> Subject: Re: [boinc_dev] High priority status message removed.
> >>>
> >>>
> >>>> You can still easily get into deadline trouble with either large
> queues,
> >>> or multiple projects and an occasional tight deadline
> >>>
> >>>
> >>>
> >>> Proof?
> >>>
> >>>
> >>>
> >>> From: McLeod, John [mailto:[email protected]]
> >>> Sent: Friday, October 3, 2014 10:54 PM
> >>> To: [email protected]; [email protected];
> >>> [email protected]; [email protected]
> >>> Subject: RE: [boinc_dev] High priority status message removed.
> >>>
> >>>
> >>>
> >>> You can still easily get into deadline trouble with either large
> queues, or
> >>> multiple projects and an occasional tight deadline.
> >>>
> >>> Sent from my Android phone using TouchDown (www.nitrodesk.com<
> http://www.nitrodesk.com<http://www.nitrodesk.com<http://www.nitrodesk.com
> >>)
> >>>
> >>> -----Original Message-----
> >>> From: Charles Elliott [[email protected]]
> >>> Received: Friday, 03 Oct 2014, 10:10PM
> >>> To: 'Jacob Klein' [[email protected]]; 'Richard Haselgrove'
> >>> [[email protected]]; McLeod, John [[email protected]];
> >>> [email protected] [[email protected]]
> >>> Subject: RE: [boinc_dev] High priority status message removed.
> >>>
> >>> On my computer, which is allocated about 300 AP WUs at a time, in late
> >>> September Boinc was running AP WUs due in late October. Then when
> October
> >>> 1 came it seemingly panicked and stopped doing anything but processing
> AP
> >>> WUs
> >>> due October 17. That behavior was useful when we could download
> thousands
> >>> of WUs, but I think it should be questioned now.
> >>>
> >>> Charles Elliott
> >>>
> >>>> -----Original Message-----
> >>>> From: boinc_dev [mailto:[email protected]] On Behalf
> >>>> Of Jacob Klein
> >>>> Sent: Friday, October 3, 2014 9:24 AM
> >>>> To: Richard Haselgrove; McLeod, John; [email protected]
> >>>> Subject: Re: [boinc_dev] High priority status message removed.
> >>>>
> >>>> I'd like to see "Prioritized to meet deadline" in the UI, next to
> >>>> "Running".
> >>>>
> >>>> ________________________________
> >>>> From: Richard Haselgrove<mailto:[email protected]>
> >>>> Sent: 10/3/2014 9:19 AM
> >>>> To: McLeod, John<mailto:[email protected]>;
> >>>> [email protected]
> >>> <mailto:[email protected]%3cmailto:[email protected]
> >
> >>> <mailto:[email protected]>
> >>>> Subject: Re: [boinc_dev] High priority status message removed.
> >>>>
> >>>> The removal followed a question and answer session at the BOINC
> >>>> workshop in Budapest earlier this week. The OS scheduler mis-
> >>>> interpretation was one that I highlighted, but there was also a
> problem
> >>>> with users thinking that High Priority was a project-chosen queue-
> >>>> jumping facility. I think we're much better off without those
> >>>> confusions over terminology, but I agree with John that it would be
> >>>> good if the reason for non-FIFO running could be marked in some way -
> >>>> if we can find a less-frightening word.
> >>>>
> >>>>
> >>>>
> >>>>> ________________________________
> >>>>> From: "McLeod, John" <[email protected]>
> >>>>> To: "[email protected]" <[email protected]>
> >>>>> Sent: Friday, October 3, 2014 2:01 PM
> >>>>> Subject: [boinc_dev] High priority status message removed.
> >>>>>
> >>>>>
> >>>>> OK, High Priority made it sound like it was running at High OS
> >>>> Scheduler Priority, but some tag that it is not in the normal RR
> >>>> schedule might be good for helping diagnose problems.
> >>>>> _______________________________________________
> >>>>> boinc_dev mailing list
> >>>>> [email protected]
> >>>>> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
> >>>>> To unsubscribe, visit the above URL and
> >>>>> (near bottom of page) enter your email address.
> >>>>>
> >>>>>
> >>>>>
> >>>> _______________________________________________
> >>>> boinc_dev mailing list
> >>>> [email protected]
> >>>> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
> >>>> To unsubscribe, visit the above URL and
> >>>> (near bottom of page) enter your email address.
> >>>> _______________________________________________
> >>>> boinc_dev mailing list
> >>>> [email protected]
> >>>> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
> >>>> To unsubscribe, visit the above URL and
> >>>> (near bottom of page) enter your email address.
> >>>
> >>> _______________________________________________
> >>> boinc_dev mailing list
> >>> [email protected]
> >>> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
> >>> To unsubscribe, visit the above URL and
> >>> (near bottom of page) enter your email address.
> >>>
> >>>
> >> _______________________________________________
> >> boinc_dev mailing list
> >> [email protected]
> >> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
> >> To unsubscribe, visit the above URL and
> >> (near bottom of page) enter your email address.
> >
> > _______________________________________________
> > boinc_dev mailing list
> > [email protected]
> > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
> > To unsubscribe, visit the above URL and
> > (near bottom of page) enter your email address.
> > _______________________________________________
> > boinc_dev mailing list
> > [email protected]
> > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
> > To unsubscribe, visit the above URL and
> > (near bottom of page) enter your email address.
>
> _______________________________________________
> boinc_dev mailing list
> [email protected]
> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
> To unsubscribe, visit the above URL and
> (near bottom of page) enter your email address.
>
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
