[ Skip to the content ]

Institute of Formal and Applied Linguistics Wiki

[ Back to the navigation ]

You are here: start » grid

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 [2018/07/15 21:18]
popel [Job monitoring] 		grid [2018/11/27 16:28]
vidra qalter works on running jobs as well
Line 10: Line 10:
 Some machines are at Malá Strana (ground floor, new server room built from Lindat budget), some are at Troja (5 km north-east). Some machines are at Malá Strana (ground floor, new server room built from Lindat budget), some are at Troja (5 km north-east).
 If you need to quickly distinguish which machine is located where, you can use your knowledge of [[https://en.wikipedia.org/wiki/Trojan_War|Trojan war]]-related heroes, ''qhost -q'', or the tables below.  If you need to quickly distinguish which machine is located where, you can use your knowledge of [[https://en.wikipedia.org/wiki/Trojan_War|Trojan war]]-related heroes, ''qhost -q'', or the tables below. 
 +
 +====== AVX instructions ======
  
 ==== Troja (cpu-troja.q) ==== ==== Troja (cpu-troja.q) ====
 ^ Name                ^ CPU type                                  ^ GHz ^cores ^RAM(GB)^ note ^ ^ Name                ^ CPU type                                  ^ GHz ^cores ^RAM(GB)^ note ^
-| achilles[1-8]       | Intel(R) Xeon(R) CPU E5-2630 v3           | 2.4 |   31 |  123  |      | +| achilles[1-8]       | Intel(R) Xeon(R) CPU E5-2630 v3           | 2.4 |   31 |  123  |  AVX enabled    | 
-| hector[1-8]         | Intel(R) Xeon(R) CPU E5-2630 v3           | 2.4 |   31 |  123  |      | +| hector[1-8]         | Intel(R) Xeon(R) CPU E5-2630 v3           | 2.4 |   31 |  123  |  AVX enabled    | 
-| helena[1-8]         | Intel(R) Xeon(R) CPU E5-2630 v3           | 2.4 |   31 |  123  |      | +| helena[1-8]         | Intel(R) Xeon(R) CPU E5-2630 v3           | 2.4 |   31 |  123  |  AVX enabled    | 
-| paris[1-8]          | Intel(R) Xeon(R) CPU E5-2630 v3           | 2.4 |   31 |  123  |      |+| paris[1-8]          | Intel(R) Xeon(R) CPU E5-2630 v3           | 2.4 |   31 |  123  |  AVX enabled    |
  
 ==== MS = Malá Strana (cpu-ms.q) ==== ==== MS = Malá Strana (cpu-ms.q) ====
Line 23: Line 25:
 | andromeda[1-13]     | AMD Opteron                     | 2.8 |    7 |   30  |      | | andromeda[1-13]     | AMD Opteron                     | 2.8 |    7 |   30  |      |
 | lucifer[1-10]       | Intel(R) Xeon(R) CPU E5620      | 2.4 |   15 |  122  |      | | lucifer[1-10]       | Intel(R) Xeon(R) CPU E5620      | 2.4 |   15 |  122  |      |
-| hydra[1-4]          | AMD Opteron SSE4 AVX            | 2.6 |   15 |  122  |      | +| hydra[1-4]          | AMD Opteron SSE4 AVX            | 2.6 |   15 |  122  |   AVX enabled   | 
-| orion[1-8]          | Intel(R) Xeon(R) CPU E5-2630 v4 | 2.2 |   39 |  122  |      |+| orion[1-8]          | Intel(R) Xeon(R) CPU E5-2630 v4 | 2.2 |   39 |  122  |   AVX enabled   |
 | cosmos              | Intel Xeon                      | 2.9 |    7 |  249  |      | | cosmos              | Intel Xeon                      | 2.9 |    7 |  249  |      |
-| belzebub            | Intel Xeon SSE4 AVX             | 2.9 |   31 |  249  |      |+| belzebub            | Intel Xeon SSE4 AVX             | 2.9 |   31 |  249  |   AVX enabled   |
 | iridium             | Intel Xeon SSE4                 | 1.9 |   15 |  501  |      | | iridium             | Intel Xeon SSE4                 | 1.9 |   15 |  501  |      |
  
Line 80: Line 82:
  
   export LC_ALL=en_US.UTF-8   export LC_ALL=en_US.UTF-8
 +  
 +If you are curious about purpose of .bashrc and .bash_profile and you need to know when they should be used you may read [[https://stackoverflow.com/a/415444|this]].
      
 ===== Basic usage ===== ===== Basic usage =====
Line 91: Line 95:
   # prepare a shell script describing your task   # prepare a shell script describing your task
 qsub -cwd -j y script.sh Hello World qsub -cwd -j y script.sh Hello World
-  # This submits your job to the default queue, which is currently ''cpu-ms.q''.+  # This submits your job to the default queue, which is currently ''cpu-*.q''.
   # Usually, there is a free slot, so the job will be scheduled within few seconds.   # Usually, there is a free slot, so the job will be scheduled within few seconds.
   # We have used two handy qsub parameters:   # We have used two handy qsub parameters:
Line 172: Line 176:
 See ''man complex'' (run it on lrc or sol machines) for a list of possible resources you may require (in addition to ''mem_free'' etc. discussed above). See ''man complex'' (run it on lrc or sol machines) for a list of possible resources you may require (in addition to ''mem_free'' etc. discussed above).
  
-''qsub **-p** -99'' +''qsub **-p** -200'' 
-Define a priority of your job as a number between -1024 and 0. Only SGE admins may use a number higher than 0. In January 2018, we changed the default to -100 (it used to be 0). SGE uses the priority to decide when to start which pending job in the queue (it computes a real number called ''prior'', which is reported in ''qstat'', which grows as the job is waiting in the queue). Note that once a job is started, you cannot "unschedule" it, so from that moment on, it is irrelevant what was its priority. You can ask for a higher priority (-99...0) if your job is urgent and/or will finish soon and you want to skip your colleagues' jobs in the queue. You should ask for lower priority (-1024..-101) if you submit many jobs at once or if the jobs are not urgent.+Define a priority of your job as a number between -1024 and 0. Only SGE admins may use a number higher than 0. In January 2018, we changed the default to -100 (it used to be 0). Please, do not use priority between -99 and 0 for jobs taking longer than a few hours, unless it is absolutely necessary for a deadline. In that case, please notify other GPU users. You should ask for lower priority (-1024..-101) if you submit many jobs at once or if the jobs are not urgent. SGE uses the priority to decide when to start which pending job in the queue (it computes a real number called ''prior'', which is reported in ''qstat'', which grows as the job is waiting in the queue). Note that once a job is started, you cannot "unschedule" it, so from that moment on, it is irrelevant what was its priority.
  
 ''qsub **-o** LOG.stdout **-e** LOG.stderr'' ''qsub **-o** LOG.stdout **-e** LOG.stderr''
Line 189: Line 193:
 ''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''
 Specify the emails where you want to be notified when the job has been **b** started, **e** ended, **a** aborted or rescheduled, **s** suspended. Specify the emails where you want to be notified when the job has been **b** started, **e** ended, **a** aborted or rescheduled, **s** suspended.
-The default is now ''-m ea'' (TODO check this) and the default email address is forwarded to you (so there is no need to use ''-M''). You can use ''-m n'' to override the defaults and send no emails.+The default is now ''-m a'' and the default email address is forwarded to you (so there is no need to use ''-M''). You can use ''-m n'' to override the defaults and send no emails.
  
 ''qsub **-hold_jid** 121144,121145'' (or ''qsub **-hold_jid** get_src.sh,get_tgt.sh'') ''qsub **-hold_jid** 121144,121145'' (or ''qsub **-hold_jid** get_src.sh,get_tgt.sh'')
Line 216: Line 220:
  
 ''**qalter**'' ''**qalter**''
-You can change some properties of already submitted jobs, which are still waiting in the queue (//pending//).+You can change some properties of already submitted jobs (both waiting in the queue and running). Changeable properties are listed in ''man qsub''.
  
 ''**man** qsub qstat qalter qhold queue_conf sge_types complex'' ''**man** qsub qstat qalter qhold queue_conf sge_types complex''

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