For some reason, the statistics are "flat-lining" in the GUI even though docker stats shows the correct values. For example, my container "tatest" has 4GB of RAM allocated:
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
85e0510920f7 stats 1.99% 79.06MiB / 256MiB 30.88% 6.34MB / 18.5MB 0B / 0B 23
b0c7fce89260 latest 0.28% 1.34GiB / 3.84GiB 34.90% 914MB / 1.01GB 0B / 0B 34
cf4fc69392eb jaeger 0.08% 12.55MiB / 512MiB 2.45% 1.73kB / 0B 0B / 0B 10
8dea7a0de998 383 0.72% 106.8MiB / 512MiB 20.87% 12MB / 12MB 0B / 0B 92
This has also been confirmed from the CLI inside the container:
Mem: 3295556K used, 730512K free, 393644K shrd, 152664K buff, 758780K cached
CPU: 0% usr 0% sys 0% nic 98% idle 0% io 0% irq 0% sirq
Load average: 0.02 0.23 0.53 2/896 284
PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND
1 0 root S 3166m 80% 1 0% arangod --server.authentication=true --config /tmp/arangod.conf
277 0 root S 1644 0% 2 0% /bin/sh
284 277 root R 1580 0% 3 0% top
However, the stats GUI under load shows the values incorrectly hitting a ceiling at 1GB even though this is not reflected by direct docker stats output.
For some reason, the statistics are "flat-lining" in the GUI even though docker stats shows the correct values. For example, my container "tatest" has 4GB of RAM allocated:
This has also been confirmed from the CLI inside the container:
However, the stats GUI under load shows the values incorrectly hitting a ceiling at 1GB even though this is not reflected by direct
docker statsoutput.