Parallel
resources are generally accessible through reservation systems, also
called batch systems. To execute their jobs, clients have to submit via
special mnemonics and chosen options a script that contains the command
line that launches the job. Options are not necessarily given in the
submission line, but can also appear in the script with a correct
syntax. Several batch systems exist. Among them, one can cite Loadleveler on IBM resources, OpenPBS or Torque , which are forks of the well-know PBS system, and OAR developped by IMAG at Grenoble, and used in the Grid'5000 Project of a research grid. Most of the submitted jobs are parallel jobs, coded from the MPI standard with an instantiation like MPICH or LAM.In
order to correctly use a batch system, a client must provide in the
submission line or in the script several information like: The number
of machines to assign, the duration that they will be used, the number
of MPI processes to use (indeed, most applications still use MPI-1.2
implementations where the number of processes is statically defined at
the spawning of the jobs).
resources are generally accessible through reservation systems, also
called batch systems. To execute their jobs, clients have to submit via
special mnemonics and chosen options a script that contains the command
line that launches the job. Options are not necessarily given in the
submission line, but can also appear in the script with a correct
syntax. Several batch systems exist. Among them, one can cite Loadleveler on IBM resources, OpenPBS or Torque , which are forks of the well-know PBS system, and OAR developped by IMAG at Grenoble, and used in the Grid'5000 Project of a research grid. Most of the submitted jobs are parallel jobs, coded from the MPI standard with an instantiation like MPICH or LAM.In
order to correctly use a batch system, a client must provide in the
submission line or in the script several information like: The number
of machines to assign, the duration that they will be used, the number
of MPI processes to use (indeed, most applications still use MPI-1.2
implementations where the number of processes is statically defined at
the spawning of the jobs).