Gitlab EE without activity almost 13 GB of RAM

Gitlab CI without activity almost 8 GB of RAM 150 processes

Part of the process from CI: enter image description here

enter image description here

In each of the same type of processes, you can see localhost: port

With what it can be connected? And how to solve the problem of "eating" RAM?

  • one
    Insert the output into the console as text - default locale
  • 2
    Not processes, but threads. Disable the display of threads in the htop settings ( Hide userland process threads ), so as not to mislead either ourselves or us - andreymal
  • Часть процессов от CI - IMHO, in vain you runners installed on the same host. - Nick Volynkin ♦
  • IMHO ... everything was done by mana. And in fact - there are enough resources, it is possible to distribute the load in any way and anywhere. - Emia

0