...
Those are just some examples of when using qlogin would be a good idea. There are also some guidelines that we ask you to follow when using qlogin sessions.
| Info |
|---|
By default, Requesting a qlogin session will try to obtain all of the slots on a single host but this is not guaranteed and it is possible that the session is shared on a host. If you specify a queue then you should also specify an appropriate number of slots for the machine type in that queue. Also, if a slot request is made explicit then, depending on the PE requested, the session could share one or more nodes with other jobs. Please be aware of this as you use your qlogin sessionallocate as many job slots as possible on a node, with a minimum of 1 job slot. It is possible that you will receive an entire node but that is not guaranteed. By attempting to allocate as many slots on a node as possible we try to increase the probability that you will have sufficient resources to experiment on the node. If you need a specific number of slots and/or require specific resources then you will need to make your qlogin resource requests explicit. |
- Qlogin sessions should not be used to "reserve" nodes or slots.
- Please only launch the number of processes that you requested. For instance, if you only request 1 slot on one machine, then please only use 1 processor core on that machine. It is quite possible that your qlogin session is shared with another job on the node and oversubscribing the node would have an adverse impact on someone else. If you need more slots, request them.
- Please logout of your interactive session when you are done to free up the resources.
- There is a default wall clock time limit of 24 hours. This can be overridden by specifying a value via
-l h_rtbut please make it reasonable.
...