![Capture d’écran 2022-09-09 à 17.13.53.png](0Q6S4L9rd3kg)

in the [compute_logs_local_process_prepared](recipe:compute_logs_local_process_prepared) recipe, we compute the following measures  : 

 1. Instant usage of resources : 
  -  **CPU_current**  : number of CPU cores used during the last minute. It is estimated as the (TotalCPUTime)/(Elapsed clock time). (e.g. if a process used 30 seconds of CPU time in 1 minute of clock time, we estimate that 0.5 CPU has been used during that minute)
  -  **memory_MB**  : the memory used during the last minute. It refers to the VmRSS from the linux /proc/[pid]/status command
 1. Cumulative usage of resources : 
   -  **cpu_time_in_minutes**  (in min) : total CPU time extracted from the linux /proc/[pid]/status command.
   -  **memory_MB_minutes**  (in MB.min) : this is the sum over each minute of the memory_MB value.
   
   
  The [compute_logs_local_process_dedupicated](recipe:compute_logs_local_process_dedupicated) is used to make sure we only keep one row per process per minute with the maximum resources usage for our minute-by-minute calculation.
  
  The [compute_logs_local_process_last](recipe:compute_logs_local_process_last) is used to take the latest log trace related to a process. It is more efficient than filtering on "complete" jobs because it also monitors aborted jobs that do not have a "complete" trace

The last thread leading to the [logs_local_process_frequencies_stats_prepared](dataset:logs_local_process_frequencies_stats_prepared) dataset computes the intervals betweens two consecutive identical jobs to monitor process frequencies.



