Generalities
===========

During a *Code_Aster* simulation, displays by default show in the message and results files (.mess/.resu) **some dimensioning characteristics of the calculation**. In particular, for each *Aster* operator, we find:


*The*characteristics of linear systems* to be built and solved (number of nodes, equations and Lagranges, size of the matrix... ),


*The*memories* *JEVEUX* * floor (to switch to Out-Of-Core [1] _
) and optimal (to switch to In-Core),


*The.*memory* *JEVEUX* required by some*external products* (e.g. MUMPS),


*The*times* CPU, system and "user" (elapsed),


*The*breakdown of the time* consumed according to the calculation steps (elementary calculation, assembly, resolution of the linear system).

This last description of the time consumed can be broken down according to different reading levels (synthetic impression, detailed and detailed by calculation increment) *via* the parameter MESURE_TEMPS/NIVE_DETAIL of the DEBUT/POURSUITE commands. In parallel mode, we add the average value, on all the processors, of the times consumed as well as their standard deviation.




.. [1] Out-Of-Core (OOC) is a mode of memory management that consists in unloading certain objects allocated by the code onto disk to release some RAM. These unloads can be automatic (triggered by the system or the JEVEUX software package) or organized by the programmer. Strategy OOC makes it possible to deal with bigger problems but these disk accesses slow down the calculation. On the other hand, In-Core (IC) mode consists in keeping the objects in RAM. This limits the size of the issues that can be accessed, but prioritizes speed.