*BSD News Article 71988


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!news.ysu.edu!usenet.ins.cwru.edu!nerd.apk.net!sed.psrw.com!psinntp	!psinntp!psinntp!howland.reston.ans.net!swrinde!newsfeed.internetmci.com!uunet!inXS.uu.net!news.artisoft.com!usenet
From: Terry Lambert <terry@lambert.org>
Newsgroups: comp.unix.bsd.misc
Subject: Re: Queuing Question
Date: Tue, 25 Jun 1996 19:23:45 -0700
Organization: Me
Lines: 41
Message-ID: <31D09F31.6DB0F89A@lambert.org>
References: <4qn5nu$svs@pulp.ucs.ualberta.ca>
NNTP-Posting-Host: hecate.artisoft.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 2.01 (X11; I; Linux 1.1.76 i486)

Nadine Leenders wrote:
] 
] I've set up a couple of queues under SunOS Release 4.1.  One the of
] queues processes large jobs that take about 1.5 to 3 hours to complete
] and the other small jobs that take about 2 minutes to complete.
] 
] Unfortuneately, it seems that the queueing system is set up to be
] first-in, first-out even between different queues so the people who
] just need a small job done are waiting hours.
] 
] As a consequence, I'd very much like the small job queue
] to process its jobs either concurrently with the large job queue
] and/or to have a higher priority than the large job queue.  Then
] people with small jobs wouldn't need to wait forever for results.
] Is there a way to do this?  Thanks muchly for any assistance you
] can provide with this.

How can you tell a job will be a small job?  Or rather, how
can the queue ordering software tell to provide the ordering
you want?

I guess one way would be to put a time limit on the job and
murder it if it goes over the limit, then use declared time
limits to determine queueing order.  This is pretty useless
without checkpoint/restart technology of some kind so you
can resurrect the murdered job at some future time.

Then, if you do that, there's got to be intentional latency
inversely relative to the amount of estimated time before the
job do Biff can't claim his job will take only 5 minutes, and
then restart it seconds after suspension to shove himself to
the front of the queue, even though his usage is massive.  He
could easily starve other (small, but larger than 5 minutes)
jobs.


                                        Terry Lambert
                                        terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.