> 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) -----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.
