Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From: markspace <-@.>
Newsgroups: comp.lang.java.programmer
Subject: Re: A quota based lock
Date: Mon, 08 Aug 2011 10:00:17 -0700
Organization: A noiseless patient Spider
Lines: 19
Message-ID: <j1p4n8$pog$1@dont-email.me>
References: <83f81158-8aee-486d-a51b-c0f7dfdbb0da@h25g2000prf.googlegroups.com> <j1oj30$tut$1@dont-email.me> <j1p40f$jua$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Mon, 8 Aug 2011 17:00:24 +0000 (UTC)
Injection-Info: mx04.eternal-september.org; posting-host="XjIWM99mD7Ijfdu600oVPA"; logging-data="26384"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18tp7nRn+ephVf8kRAmj7kK7QvPJu3ydSE="
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
In-Reply-To: <j1p40f$jua$1@dont-email.me>
Cancel-Lock: sha1:j58mHRV6NWEaP/WhKlxfVvYZ3PE=
Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:6870

On 8/8/2011 9:48 AM, Knute Johnson wrote:
>
> I like that idea with a twist, have the higher priority jobs get put in
> the queue closer to the top.


No, see this is why "one little twist" doesn't work.  Higher priority 
jobs will then starve out the lower priority jobs if there are enough of 
them.  Putting them in "closer" will bump them ahead of other jobs, 
which may stay permanently in the back of the queue if there are enough 
bumps.


FIFO scheduling is best until you figure out something else that 
actually works.  Perturbing that FIFO algorithm isn't likely to work and 
will cause starvation, as noted above.