On Mon, 9 May 2011 at 14:17 -0000, Reuti wrote:
> > I also have always had problems with the usage of "queue" in Grid
> > Engine.
> >
> > To me a queue would be a set of jobs waiting to run, usually with
> > an ordering (first come first serve, priority, random).
> >
> > Grid Engine seems to apply 'queue' to a group of resources with a
> > common set of configuration/attributes.
>
> Yes, "queue" is something to do work in, not to wait. But it maybe
> already be defined this way in POSIX.
Really? To me a queue is where you wait until you get assigned to a
worker. You have the email queue (mail waiting to go out or waiting
to be delivered). In a network device the packet queue is where
packets sit until they are able to be processed.
As someone else pointed out, there might be a German/English language
issue in play here. What is the German word for this concept
"something to do work in, not to wait"?
This next bit is quite off topic. Feel free to ignore...
Using google translate starting from English "queue", most of the
German translations map back to about the same concept in English.
** A few double translations (en->de->en) go a little off the mark.
queue (noun) -> queue ->
1. queue
2. cue ** (pronounced the same, but very different concept)
(most of the other nouns are strange, but do translate back to queue
in some form)
queue (verb) -> anstehen ->
1. queue
2. hesitate (**)
3. queue up
4. befit (**)
5. stand in line
6. be due
7. be on the agenda
queue (verb) -> Schlange stehen ->
1. queue
2. stand in line
queue (verb) -> sich anstellen ->
1. queue
2. behave (**)
3. queue up
4. act (**)
5. line up
6. stand in line
7. make a fuss (**)
8. act up (**)
queue (verb) -> eine Schlange bilden ->
1. queue
> > As a simplified user concept the use of the word 'queue' can
> > convey a useful model and also be a method to apply differing
> > defaults to a job ("Submit to the short job queue").
>
> No. Specify resource requests in time, memory,... and SGE will
> select an appropriate queue for you. Submitting to a queue is
> Torque/PBS style.
Actually, this is what I prefer (request what you really want), but
I've been unable to eradicate the concept of distinct queues from our
users. The Internet is full of simplified user instructions to submit
jobs with "-q queuename" (unfortunately they usually don't show the
implementing SGE configurations).
I dislike the fact that someone created "long", "medium" and "short"
as SGE queues for our users and told them all they need to do is
select the correct queue for their job. I can't change the parameters
of these without users getting unexpected behavior changes.
I do want to have resources with different wall clock limits so that
heavy compute users don't grab all of the available resources for
several weeks. I think this is/should be another FAQ with a few
completely worked example configurations.
Do people actually have lots of queues? Or would just 'interactive'
and 'batch' work suitably as queues?
I've picked up a lot of good information in the past couple of weeks.
Now I need to get some time to work with things and try some more
experiments.
Thanks,
Stuart
--
I've never been lost; I was once bewildered for three days, but never lost!
-- Daniel Boone
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
