[ 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 [2018/06/08 09:59]
vodrazka [ÚFAL Grid Engine (LRC)] - update info to match new cluster
grid [2018/07/06 11:40]
lauschmannova [Advanced usage] there are now 10 different sols rather than 8
Line 1: Line 1:
 ====== ÚFAL Grid Engine (LRC) ====== ====== ÚFAL Grid Engine (LRC) ======
  
-LRC (Linguistic Research Cluster) is a name of ÚFAL's computational grid/cluster, which has (as of 2018/06) about 392 CPU cores (26 servers + 10 submission heads), with a total 2.TiB of RAM. It uses [[https://en.wikipedia.org/wiki/Oracle_Grid_Engine|(Sun/Oracle/Son of) Grid Engine]] software (SGE) for job scheduling etc. You can submit many computing tasks (jobs) at once, they will be placed in a queue and once a machine (slot) with the required capabilities (e.g. RAM, number of cores) is available, your job will be executed (scheduled) on this machine. This way we can maximize the usefulness of the computing resources and divide it among users in a fair way.+LRC (Linguistic Research Cluster) is a name of ÚFAL's computational grid/cluster, which has (as of 2018/06) about 1728 CPU cores (65 servers + 10 submission heads), with a total 7.TiB of RAM. It uses [[https://en.wikipedia.org/wiki/Oracle_Grid_Engine|(Sun/Oracle/Son of) Grid Engine]] software (SGE) for job scheduling etc. You can submit many computing tasks (jobs) at once, they will be placed in a queue and once a machine (slot) with the required capabilities (e.g. RAM, number of cores) is available, your job will be executed (scheduled) on this machine. This way we can maximize the usefulness of the computing resources and divide it among users in a fair way.
  
 If you need GPU processing, see a special page about our [[:gpu|GPU cluster called DLL]] (which is actually a subsystem of LRC with an independent queue ''gpu-ms.q''). If you need GPU processing, see a special page about our [[:gpu|GPU cluster called DLL]] (which is actually a subsystem of LRC with an independent queue ''gpu-ms.q'').
Line 23: Line 23:
 | 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 |  123       |+| hydra[1-4]          | AMD Opteron SSE4 AVX            | 2.6 |   15 |  122  |      | 
 +| orion[1-8]          | Intel(R) Xeon(R) CPU E5-2630 v4 | 2.2 |   39 |  122  |      | 
 +| cosmos              | Intel Xeon                      | 2.9 |    7 |  249  |      | 
 +| belzebub            | Intel Xeon SSE4 AVX             | 2.9 |   31 |  249  |      | 
 +| iridium             | Intel Xeon SSE4                 | 1.9 |   15 |  501       |
  
 +Machines from old cluster (do not use!):
 +
 +^ Name                ^ CPU type and flags              ^ GHz ^cores ^RAM(GB)^ note ^
 | fireball[1-10]      | Intel Xeon           | 3.0 |    4 |   32 | removed | | fireball[1-10]      | Intel Xeon           | 3.0 |    4 |   32 | removed |
 | hyperion[1-9]       | Intel Xeon           | 3.0 |    4 |   32 | removed | | hyperion[1-9]       | Intel Xeon           | 3.0 |    4 |   32 | removed |
-| orion[1-6]          | Intel Xeon           | 2.3 |    8 |   32 | removed | 
-| orion[7-10]         | Intel Xeon           | 2.0 |    4 |   32 | removed | 
 | tauri[1-10]         | Intel Xeon           | 3.0 |    4 |   32 | removed | | tauri[1-10]         | Intel Xeon           | 3.0 |    4 |   32 | removed |
-| cosmos              | Intel Xeon           | 2.9 |    8 |  256 | migration pending | +| twister[1,2]        | Intel Xeon SSE4      | 2.4 |    8 |   48 | moved to GPU cluster|
-| belzebub            | Intel Xeon SSE4 AVX  | 2.9 |   32 |  256 | migration pending | +
-| iridium             | Intel Xeon SSE4      | 1.9 |   16 |  512 | migration pending | +
-| twister[1,2]        | Intel Xeon SSE4      | 2.4 |    8 |   48 | migration pending |+
  
 <html><!-- <html><!--
Line 55: Line 57:
 ^ Name                ^ CPU type                        ^ GHz ^cores ^ RAM(GB) ^ note  ^ ^ Name                ^ CPU type                        ^ GHz ^cores ^ RAM(GB) ^ note  ^
 | sol[1-10]           | Intel(R) Xeon(R) CPU E5345      | 2.3 |    7 |   31    | you can ssh here and compute or submit jobs | | sol[1-10]           | Intel(R) Xeon(R) CPU E5345      | 2.3 |    7 |   31    | you can ssh here and compute or submit jobs |
 +| lrc[12]             | Intel(R) Xeon(R) CPU E5-2630 v4 | 2.2 |    4 |    4    | you can submit jobs here or monitor job execution - NO COMPUTATION IS ALLOWED HERE !!! |
  
 You can ssh to one of the **sol machines** and submit jobs from here. It is allowed to compute here, which is useful e.g. when you have a script which submits your jobs, but it also collects statistics from the jobs outputs (and possibly submits new jobs conditioned on the statistics). However, the sol machines are relatively slow and may be occupied by your colleagues, so for bigger (longer) tasks, always prefer submission as separate jobs. You can ssh to one of the **sol machines** and submit jobs from here. It is allowed to compute here, which is useful e.g. when you have a script which submits your jobs, but it also collects statistics from the jobs outputs (and possibly submits new jobs conditioned on the statistics). However, the sol machines are relatively slow and may be occupied by your colleagues, so for bigger (longer) tasks, always prefer submission as separate jobs.
Line 62: Line 65:
 Add the following line into your '~/.bash_profile'. Add the following line into your '~/.bash_profile'.
  
-  source /opt/LRC/common/settings.sh+  source /opt/LRC/sge_profile 
 + 
 +Or call one of these scripts directly: 
 + 
 +  /opt/LRC/common/settings.sh (for bash)  
 +  /opt/LRC/common/settings.csh (for tcsh/csh)
  
 This detects if you are on one of the cluster machines (including sol) and sets env variables accordingly. It also prints a status message. This detects if you are on one of the cluster machines (including sol) and sets env variables accordingly. It also prints a status message.
Line 181: Line 189:
 ''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.
  
 ''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 253: Line 262:
  
 and you execute it now simply with ''qsub script.sh''. and you execute it now simply with ''qsub script.sh''.
 +
 +=== ~/.sge_request ===
 +
 +You can change the defaults for any option by creating a personal configuration file ''~/.sge_request''. For example, you can add there a line ''-m n'', so you will get no email notifications (unless overridden from the command line or in-script options).
  
 === Array jobs === === Array jobs ===
Line 275: Line 288:
 === Ssh to random sol === === Ssh to random sol ===
 Ondřej Bojar suggests to add the following alias to your .bashrc (cf. [[#sshcwd]]): Ondřej Bojar suggests to add the following alias to your .bashrc (cf. [[#sshcwd]]):
-<code>alias cluster='comp=$(($RANDOM /4095 +1)); ssh -o "StrictHostKeyChecking no" sol$comp'</code>+<code>alias cluster='comp=$(( (RANDOM % 10) +1)); ssh -o "StrictHostKeyChecking no" sol$comp'</code>
  
 ===== Job monitoring ===== ===== Job monitoring =====

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