[ 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
grid [2020/05/06 14:44]
ufal [Other]
grid [2021/04/13 11:43] (current)
vodrazka [MS = Malá Strana (cpu-ms.q)]
Line 23: Line 23:
  
 ^ Name                ^ CPU type and flags              ^ GHz ^cores ^RAM(GB)^ note ^ ^ Name                ^ CPU type and flags              ^ GHz ^cores ^RAM(GB)^ note ^
-| andromeda[1-13] ​    | AMD Opteron ​                    | 2.8 |    7 |   ​30 ​ |      | 
-| lucifer[1-10] ​      | Intel(R) Xeon(R) CPU E5620      | 2.4 |   15 |  122  |      | 
 | hydra[1-4] ​         | AMD Opteron SSE4 AVX            | 2.6 |   15 |  122  |   AVX enabled ​  | | 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  |   AVX enabled ​  | | orion[1-8] ​         | Intel(R) Xeon(R) CPU E5-2630 v4 | 2.2 |   39 |  122  |   AVX enabled ​  |
-| cosmos ​             | Intel Xeon                      | 2.9 |    7 |  249  |      | 
 | belzebub ​           | Intel Xeon SSE4 AVX             | 2.9 |   31 |  249  |   AVX enabled ​  | | 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  |      |
- 
-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 | 
-| hyperion[1-9] ​      | Intel Xeon           | 3.0 |    4 |   32 | removed | 
-| tauri[1-10] ​        | Intel Xeon           | 3.0 |    4 |   32 | removed | 
-| twister[1,​2] ​       | Intel Xeon SSE4      | 2.4 |    8 |   48 | moved to GPU cluster| 
  
 <​html><​!-- <​html><​!--
Line 58: Line 47:
 === Submit hosts / test machines === === Submit hosts / test machines ===
 ^ 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.|    7 |   31    | you can ssh here and compute or submit jobs |+| sol[1-8]           | Intel(R) Xeon(R) CPU E5-2630 v3 | 2.|    7 |   28    | 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 !!! | | 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 !!! |
  
Line 333: Line 322:
   * You can use environment variables ''​$JOB_ID'',​ ''​$JOB_NAME''​.   * You can use environment variables ''​$JOB_ID'',​ ''​$JOB_NAME''​.
   * One job can submit other jobs (but be careful with recursive:​-)). A job submitted to the CPU cluster may submit GPU jobs (to the ''​qpu.q''​ queue).   * One job can submit other jobs (but be careful with recursive:​-)). A job submitted to the CPU cluster may submit GPU jobs (to the ''​qpu.q''​ queue).
-  * It is important, that the files that are sourced during a login such as .bash_profile,​ .profile, .bashrc, .login etc. don't produce any output when a non-interactive login is done. If they do, changes ​are that your job will run, but that the batch system is unable to deliver to you the standard output and error files. In that case the status of your job will be '​E'​ after the job is finished. Here is an example how you can test in a .bash_profile or .bashrc if this is an interactive login:+  * It is important, that the files that are sourced during a login such as .bash_profile,​ .profile, .bashrc, .login etc. don't produce any output when a non-interactive login is done. If they do, chances ​are that your job will run, but that the batch system is unable to deliver to you the standard output and error files. In that case the status of your job will be '​E'​ after the job is finished. Here is an example how you can test in a .bash_profile or .bashrc if this is an interactive login:
 <​code>​ <​code>​
 unset INTERACTIVE unset INTERACTIVE

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