Adapp: Introduction

Adapp is the architecture at IDRIS dedicated to intensive pre- and post-processing and to the management of great masses of data. Adapp must only be used for jobs with the following characteristics:

  • Performing many I/Os (e.g. re-combining files)
  • Requiring a large amount of memory (e.g. mesh generating and partitioning)

This pre-/post-processing Adapp architecture contains only 4 compute nodes, each one having:

  • Four 8-core Intel Westmere processors at 2,67GHz (or 32 cores)
  • 1 TB of memory
  • 8 internal disks of 600 GB

Consequently, the use of these nodes is subject to the following restrictions:

  • Maximum Elapsed time of 20h for both sequential and parallel jobs
  • Maximum reservation of 32 cores (or 1 compute node)
  • Maximum of 100 GB of memory for a sequential execution or 30 GB per reserved core in parallel classes (MPI, OpenMP or hybrid)

Interactive and batch limits may be consulted at class structures for Ada/Adapp.

Please note that you just have to add the keyword
# @ requirements = (Feature == “PREPOST”)
for your job to be submitted on Adapp. However, to be able to run, it must respect the limits indicated above (Elapsed time, number of cores and memory) or it will remain in waiting.

From Adapp (interactive or batch), the Ergon archive server HOME is directly accessible in read/write via the $ARCHIVE environment variable (thanks to a GPFS setup).

For more information concerning the available software or librairies, the architecture or the usage of the Adapp resources, see here.