Usage CPU immodéré sans raison

[gilluc]

je viens d'installer espocrm depuis 1 semaine.
j'ai créé 10 comptes, 10 contacts et 1 opportunité...pour tester...
il n'y a personne loggé ...
voici la consommation cpu:

2026-08-21 08:30:02 / CPU / 5236387223b3 espocrm-daemon 213.92% 158MiB / 22.92GiB
2026-08-21 08:45:02 / CPU / 5236387223b3 espocrm-daemon 96.99% 35.8MiB / 22.92GiB
2026-08-21 09:00:02 / CPU / 5236387223b3 espocrm-daemon 140.57% 254.4MiB / 22.92GiB
2026-08-21 09:15:02 / CPU / 5236387223b3 espocrm-daemon 78.74% 168.1MiB / 22.92GiB

j'ai d'autres containers sur cette machine OVH 8 coeurs xeon 24 go ram qui consomment rarement plus de 5% ...

comment c'est possible de consommer autant de cpu quand ya personne connecté ???

[lazovic]

Hi gilluc,

Please clarify whether any integrations (Google, Outlook) are working? Are any email accounts connected (with IMAP)?

Please also keep in mind that you can monitor the load in real time with the following command; use it in the terminal:

docker container stats espocrm-daemon

You can also go directly into the container and use the following command:

htop

[gilluc]

Hi gilluc,

Please clarify whether any integrations (Google, Outlook) are working? Are any email accounts connected (with IMAP)?

Please also keep in mind that you can monitor the load in real time with the following command; use it in the terminal:

docker container stats espocrm-daemon

You can also go directly into the container and use the following command:

htop

No integration at all
no email connected at all

it's just a clean install of espocrm with docker / i used the provided docker-compose.yml here

https://docs.espocrm.com/administration/docker/installation/#docker-compose

of course, the 4 lines i provided are from "docker container stats espocrm-daemon" i am not a noob!
please re read my first post!

[yuri]

These are likely very short burst (much shorter than a second). The background daemon spawns parallel processes to handle jobs. The default configuration is suitable for a real production use with multiple users.

You can decrease 'Jobs Pool Concurrency Number' under Administration > Job Settings, also increase 'Daemon Interval'. If you expect to have very few users, you can disable 'Jobs Run in Parallel'. You can also limit resource usage for the daemon container.

Such short spikes should not be a problem. The application is pretty large.

We did some tests and observed similar spikes, but the CPU% numbers were somewhat lower than yours.

[gilluc]

today trace:

2026-08-23 16:00:03 / CPU / 5236387223b3 espocrm-daemon 189.30% 36.42MiB / 22.92GiB 0.16% 1.92GB / 2.04GB 8.53MB / 215MB 2
2026-08-23 16:30:03 / CPU / 5236387223b3 espocrm-daemon 256.39% 36.45MiB / 22.92GiB 0.16% 1.93GB / 2.05GB 8.53MB / 215MB 2
2026-08-23 17:00:03 / CPU / 5236387223b3 espocrm-daemon 205.59% 84.97MiB / 22.92GiB 0.36% 1.94GB / 2.05GB 8.53MB / 216MB 3
2026-08-23 17:15:03 / CPU / 5236387223b3 espocrm-daemon 105.57% 36.52MiB / 22.92GiB 0.16% 1.94GB / 2.06GB 8.53MB / 217MB 2
2026-08-23 17:45:03 / CPU / 5236387223b3 espocrm-daemon 116.05% 36.54MiB / 22.92GiB 0.16% 1.95GB / 2.07GB 8.53MB / 217MB 2
2026-08-23 18:00:04 / CPU / 5236387223b3 espocrm-daemon 237.85% 36.57MiB / 22.92GiB 0.16% 1.95GB / 2.07GB 8.53MB / 218MB 2
2026-08-23 18:30:04 / CPU / 5236387223b3 espocrm-daemon 244.01% 96.18MiB / 22.92GiB 0.41% 1.96GB / 2.08GB 8.53MB / 218MB 4
2026-08-24 02:15:03 / CPU / 046f00a9fd54 espocrm-websocket 18.08% 22.27MiB / 22.92GiB 0.09% 12.4MB / 2.15MB 3.51MB / 49.2kB 3
2026-08-24 02:30:04 / CPU / 046f00a9fd54 espocrm-websocket 18.76% 22.29MiB / 22.92GiB 0.09% 12.4MB / 2.15MB 3.51MB / 49.2kB 3
2026-08-24 10:00:03 / CPU / 5236387223b3 espocrm-daemon 235.45% 91.93MiB / 22.92GiB 0.39% 2.18GB / 2.31GB 8.53MB / 241MB 3
2026-08-24 11:30:03 / CPU / 5236387223b3 espocrm-daemon 195.84% 37.77MiB / 22.92GiB 0.16% 2.2GB / 2.33GB 8.53MB / 244MB 2
2026-08-24 12:15:03 / CPU / 5236387223b3 espocrm-daemon 90.11% 37.81MiB / 22.92GiB 0.16% 2.21GB / 2.34GB 8.53MB / 245MB 2
2026-08-24 12:45:04 / CPU / 5236387223b3 espocrm-daemon 90.64% 37.84MiB / 22.92GiB 0.16% 2.22GB / 2.35GB 8.53MB / 245MB 2
2026-08-24 13:15:04 / CPU / 5236387223b3 espocrm-daemon 111.03% 38.58MiB / 22.92GiB 0.16% 2.22GB / 2.36GB 8.53MB / 246MB 2
2026-08-24 14:00:04 / CPU / 5236387223b3 espocrm-daemon 198.92% 86.45MiB / 22.92GiB 0.37% 2.23GB / 2.37GB 8.53MB / 247MB 3

[gilluc]

for a "very short burst (much shorter than a second)", you can see how lucky i am to capture so many spikes every 15 minutes !!!

it is not acceptable for me as no user was connected since yesterday...

[yuri]

Daemon runs a cycle every 10 seconds, it starts multiple sub-processes in parallel. They all execute say within 0.1 second. These spikes will be regularly caught by `docker run stats` that prints the snapshot every 1 second.

As I mentioned above there are parameters to configure the daemon. The number of users connected has nothing to do with background jobs as I mentioned above.

100%-200%CPU for 0.1s is a fairly small load. Yet you can decrease it substantially by configuring the parameters.

Please no need to use multiple exclamation marks, we appreciate when users adhere to more respectful language on our forum. Multiple people have already spent hours just on your post. Yet we don't have any contractual obligation to provide help.