3. Displays#

At the start of the execution, a header is displayed. There you will find:

  • The precise identification of the version used: version number, date of latest changes,

  • The date and time of the start of the execution,

  • The name, architecture, operating system of the machine,

  • The language used to display messages,

  • The type of parallelism available (MPI /OpenMP), the number of processors allocated,

  • The version of the libraries used (when available) for hdf5, med, mumps, scotch,

  • Then several information on the distribution of the memory. For example:

Memory limit for dynamic allocation: 1894.40 MB
  added at process initialization: 1125.45 MB
         Target process limit: 3019.85 MB

Which means:

  • 1894.40 MB is the amount of memory reserved for internal objects. In detail: The user requested 1536.00 MB. We removed 10% (by default value of RESERVE_MEMOIRE/POURCENTAGE), 1382.40 MB left. 512.00 MB is systematically added for Jeveux internal objects, i.e. 1894.40 MB.

  • 1125.45 MB is consumed simply by starting the execution (loading the executable, associated dynamic libraries, etc.). It is a measured value.

  • 3019.85 MB is the sum of the previous two values. It’s the amount of memory total that should not be exceeded.

During execution, based on dynamic allocations made, when this value varies by more than 10% (up or down), a message of this type informs the user:

The memory currently consumed excluding JEVEUX is 214.08 MB.
The dynamic allocation limit JEVEUX is set at 41.92 MB.

At the end of execution, a report indicates whether the same calculation can be restarted with less memory:

The memory requested at launch is overestimated, it is 256 MB.
The peak memory used is 216.02 MB.

or if more memory is required (indeed, depending on the platform, the maximum limit can be exceeded without the system having interrupted the calculation):

The memory requested at launch is underestimated, it is 256 MB.
The peak memory used is 273.22 MB.