Closed jonastelzio closed 3 years ago
The high idle usage is caused by the 1s
interval healthcheck on db and grafana.
Changing this to 10s
has mitigated this a lot, but the CPU still spikes every 10s.
@jonastelzio sorry, intervall healthcehck of docker ?
what is the docker version ?
@adubovikov I changed these two lines in the docker-compose.yml file to be 10s
instead of 1s
:
https://github.com/sipcapture/homer7-docker/blob/master/heplify-server/hom7-prom-all/docker-compose.yml#L84
https://github.com/sipcapture/homer7-docker/blob/master/heplify-server/hom7-prom-all/docker-compose.yml#L189
Docker version:
$ docker version
Client:
Version: 19.03.6-ce
API version: 1.40
Go version: go1.13.4
Git commit: 369ce74
Built: Fri May 29 04:01:26 2020
OS/Arch: linux/amd64
Experimental: false
Server:
Engine:
Version: 19.03.6-ce
API version: 1.40 (minimum version 1.12)
Go version: go1.13.4
Git commit: 369ce74
Built: Fri May 29 04:01:57 2020
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.3.2
GitCommit: ff48f57fc83a8c44cf4ad5d672424a98ba37ded6
runc:
Version: 1.0.0-rc10
GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd
docker-init:
Version: 0.18.0
GitCommit: fec3683
Hey there!
Just installed Homer 7.7 with the docker image - man that is awesome! I've installed it on AWS on a t3.medium instance, using these exact commands:
However, when it's just sitting there not receiving even the shadow of a sip package from anywhere, the CPU usage is at ~30% constantly. Here us what
docker stats
shows me:This is just after installation, and there is no traffic being directed to the instance at all.