[ Skip to the content ]

Institute of Formal and Applied Linguistics Wiki


[ Back to the navigation ]

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
grid [2019/02/14 17:49]
dusek [Advanced usage]
grid [2020/01/07 15:07]
popel [Advanced usage]
Line 172: Line 172:
 ''​-q '​*@hector[14]'''​ to submit on hector1 or hector4, ''​-q '​*@hector[14]'''​ to submit on hector1 or hector4,
 ''​-q '​[tm]*@!(hector*|iridium)'''​ to submit on any troja/ms machine except hectors and iridium. ''​-q '​[tm]*@!(hector*|iridium)'''​ to submit on any troja/ms machine except hectors and iridium.
-However, usually you should specify just the queue (troja-all.q vs. ms-all.q), not a particular machine, and instead use ''​-l''​ to specify the needed resources in a general way.+However, usually you should specify just the queue (cpu-troja.q vs. cpu-ms.q), not a particular machine, and instead use ''​-l''​ to specify the needed resources in a general way.
  
 ''​qsub **-l** ...''​ ''​qsub **-l** ...''​
Line 190: Line 190:
  
 ''​qsub **-b** y''​ ''​qsub **-b** y''​
-Treat ''​script.sh''​ (or whatever is the name of the command you execute) as a binary, i.e. don't search for [[#​in-script options]] within the file, don't transfer it to the qmaster and then to the execution node. This makes the execution a bit faster and it may prevent some rare but hard-to-detect errors caused SGE interpreting the script. The script must be available on the execution node via NFS, Lustre (which is our case), etc. With ''​-b y''​ (shortcut for ''​-b yes''​),​ ''​script.sh''​ can be script or a binary. With ''​-b n''​ (which is the default for ''​qsub''​),​ ''​script.sh''​ must be a script (text file).+Treat ''​script.sh''​ (or whatever is the name of the command you execute) as a binary, i.e. don't search for [[#​in-script options]] within the file, don't transfer it to the qmaster and then to the execution node. This makes the execution a bit faster and it may prevent some rare but hard-to-detect errors caused SGE interpreting the script. The script must be available on the execution node via NFS, Lustre (which is our case), etc. With ''​-b y''​ (shortcut for ''​-b yes''​),​ ''​script.sh''​ can be an executable ​script or a binary ​(and you must provide full path, e.g. ''​./​script.sh''​). With ''​-b n''​ (which is the default for ''​qsub''​),​ ''​script.sh''​ must be a script (text file).
  
 ''​qsub **-M** popel@ufal.mff.cuni.cz,​rosa@ufal.mff.cuni.cz **-m** beas''​ ''​qsub **-M** popel@ufal.mff.cuni.cz,​rosa@ufal.mff.cuni.cz **-m** beas''​
Line 311: Line 311:
   * ''​cat /​opt/​LRC/​REPORTER/​LRC-UFAL/​stats/​userlist.weight''​ -- all users sorted according to their activity (number of submitted jobs × their average duration), updated each night   * ''​cat /​opt/​LRC/​REPORTER/​LRC-UFAL/​stats/​userlist.weight''​ -- all users sorted according to their activity (number of submitted jobs × their average duration), updated each night
  
-  * [[http://​ufaladm2/​munin/​ufal.hide.ms.mff.cuni.cz/​lrc-headnode.ufal.hide.ms.mff.cuni.cz/​index.html|Munin:​ graph of cluster usage by day and user]] and  [[http://​ufaladm2/​munin/​ufal.hide.ms.mff.cuni.cz/​apophis.ufal.hide.ms.mff.cuni.cz/​index.html|Munin monitoring of Apophis ​disk server]] (both accessible only from ÚFAL network)+  * [[https://ufaladm2.ufal.hide.ms.mff.cuni.cz/​munin/​ufal.hide.ms.mff.cuni.cz/​lrc-master.ufal.hide.ms.mff.cuni.cz/​index.html|Munin:​ graph of cluster usage by day and user]] and  [[https://ufaladm2.ufal.hide.ms.mff.cuni.cz/​munin/​ufal.hide.ms.mff.cuni.cz/​nfs-core.ufal.hide.ms.mff.cuni.cz/​index.html|Munin monitoring of disk storage]] (both accessible only from ÚFAL network)
  
 ===== Profiling ===== ===== Profiling =====

[ Back to the navigation ] [ Back to the content ]