Open engageub opened 2 weeks ago
github-actions[bot]
commented
2 weeks ago @qdm12 is more or less the only maintainer of this project and works on it in his free time. Please:
elmagow
commented
2 weeks ago Same for me on latest Fedora. Not as high usage, but still on top of my cpu usage with my server doing nothing
qdm12
commented
2 weeks ago OpenVPN version: 2.6 is the difference. Try using OPENVPN_VERSION=2.5?
engageub
commented
2 weeks ago Hi,
Thank you for the response. Yes, OPENVPN_VERSION=2.5 reduces the CPU similar to v3.37.0. However, there is a problem with consistency in the latest version.
When I run the command sudo docker stats <gluetun_container_name> for about a minute to get the stats, the CPU utilization suddenly spikes to 100% and comes back to normal, whereas with v3.37.0 this is not the case.
Thank you
qdm12
commented
1 week ago reduces the CPU similar to v3.37.0.
Do you also have the problem with v3.38.0?
Anyway if Openvpn 2.6 is at fault, there isn't much I can do as far as I know, nothing changed except the openvpn version. Still a strange issue... It might be worth reporting it to the OpenVPN dev team? 🤔
the CPU utilization suddenly spikes to 100% and comes back to normal, whereas with v3.37.0 this is not the case.
I'm not sure I understand this fully, the CPU spikes to 100% for Gluetun only, or for the entire machine, and for how long? Does it happen only when querying docker stats?
engageub
commented
1 week ago Do you also have the problem with v3.38.0?
v3.38.0 is slightly better than v3.37.0 when compared to memory usage. v3.38.0 was consuming about 56 MB where as v3.37.0 was consuming about 64 MB. CPU is normal in this version.
Anyway if Openvpn 2.6 is at fault, there isn't much I can do as far as I know, nothing changed except the openvpn version. Still a strange issue... It might be worth reporting it to the OpenVPN dev team? 🤔
If OpenVPN version is the only problem, then it is supposed to be informed to them to resolve the issue.
I'm not sure I understand this fully, the CPU spikes to 100% for Gluetun only, or for the entire machine, and for how long? Does it happen only when querying
docker stats?
I started the container with --cpus=1 options in 4 core machine. The CPU is 100% only for gluetun container displayed by docker stats command.
This can also be tested on Play with Docker website directly without using --cpus option.
engageub
commented
12 hours ago In v3.37.0, I also observed that the default health checks were consuming more CPU. A 5-second interval ping is too aggressive for health checks. By disabling health checks and removing the exposed ports, CPU utilization has drastically reduced. I was only able to run 100 containers earlier, which reached about 90% CPU utilization. After removing health checks and deleting the ports, 100 containers are now using only about 10% CPU in total. This shows a significant variation in CPU usage with health checks enabled. Memory utilization has also dropped below 20 MB for each container after removing health checks and exposed ports.
Thank you
Is this urgent?
None
Host OS
Ubuntu 22
CPU arch
x86_64
VPN service provider
OPENVPN
What are you using to run the container
docker run
What is the version of Gluetun
Running version latest built on 2024-05-18T18:08:57.405Z (commit 4218dba)
What's the problem 🤔
When the docker image qmcgaw/gluetun is used. The CPU utilization of the container goes to about 100% of 1 CORE where as the following image qmcgaw/gluetun:v3.37.0 uses less than 1% of 1 CORE. Could you please look into the latest version and compare it with v3.37.0.
Share your logs (at least 10 lines)
Share your configuration