On Wed, 9 Jan 2013 16:58:24 +0100 Reuti Reuti wrote: Hi Reuti,
[...] > > So, from understanding, I'm telling the system twice that the queue > > has X slots. > > If you have only one queue: yes, it's twice the same information. > > But if you have more than one queue, the host complex is the slot > count across all queues in total per host (and you could set it to an > arbitrary value like 100 on a queue level as it's limited anyway - > but then the `qstat -f` output would be confusing listing something > like 0/8/100 as 8 are used out of 100. So it's better as you > suggested below to define two hostgroups and attach the correct value > on a queue level too). Sorry Reuti, but which are the implications of having that information wrong? (i.e: 0/8/100)? Something at scheduler level?? > > I've been doing some tests removing slots values in queues, and OGS > > behaves as desired: not allocating too many jobs in one node even if > > the queue has free slots ot if the node is already running enough > > jobs, but, as I found no examples of this conf, I'm wondering if > > this is correct to define queue slots as a maximum and then define > > hosts with slots complex_values. > > You mean you lowered the number of slots on a queue level for testing > purpose? nope, sorry for my explanation. I configured a queue with 9999 slots, and defined host complex slot value. I saw no oversubscription at all. [I'll come back with preemption questions in the future] > -- Reuti Thanks a lot for your reply, Arnau _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
