Originally assigned to: @oschwartz10612 on GitHub.
Describe the Bug
I have a 4-core host running a Newt container and an Olm container. The Olm process continuously uses around 10% CPU, which is not extreme, but it's pretty much at the top of top, which strikes me as odd. Newt stays below 1%.
Environment
OS Type & Version: Debian GNU/Linux 12 (bookworm)
Pangolin Version: 1.14.1
Gerbil Version: 1.3.0
Olm Version: 1.3.0
To Reproduce
Can't report much details as it is, this is the compose file I have to deploy Olm (I'm not using host network on purpose):
Less CPU usage, or at least a confirmation that more CPU usage is expected.
Originally created by @asardaes on GitHub (Jan 6, 2026).
Original GitHub issue: https://github.com/fosrl/olm/issues/73
Originally assigned to: @oschwartz10612 on GitHub.
### Describe the Bug
I have a 4-core host running a Newt container and an Olm container. The Olm process continuously uses around 10% CPU, which is not extreme, but it's pretty much at the top of `top`, which strikes me as odd. Newt stays below 1%.
### Environment
- OS Type & Version: Debian GNU/Linux 12 (bookworm)
- Pangolin Version: 1.14.1
- Gerbil Version: 1.3.0
- Olm Version: 1.3.0
### To Reproduce
Can't report much details as it is, this is the compose file I have to deploy Olm (I'm not using host network on purpose):
```yaml
secrets:
olm_config:
file: olm_config.json
services:
olm:
image: fosrl/olm
container_name: olm
restart: unless-stopped
cap_add:
- NET_ADMIN
environment:
CONFIG_FILE: /run/secrets/olm_config
DISABLE_HOLEPUNCH: "true"
secrets:
- olm_config
devices:
- /dev/net/tun:/dev/net/tun
```
Besides the sensitive stuff, the JSON doesn't have anything out of the ordinary:
```json
{
"org": "",
"userToken": "",
"mtu": 1280,
"dns": "192.168.50.1",
"upstreamDNS": ["9.9.9.9:53"],
"interface": "olm",
"logLevel": "INFO",
"enableApi": false,
"httpAddr": "",
"socketPath": "/var/run/olm.sock",
"pingInterval": "3s",
"pingTimeout": "5s",
"disableHolepunch": true,
"overrideDNS": false,
"disableRelay": false,
"tlsClientCert": ""
}
```
### Expected Behavior
Less CPU usage, or at least a confirmation that more CPU usage is expected.
@oschwartz10612 commented on GitHub (Jan 8, 2026):
We are actually working on improving CPU usage for olm especially because of mobile devices! I hope to have some improvements in the next release.
<!-- gh-comment-id:3721371283 -->
@oschwartz10612 commented on GitHub (Jan 8, 2026):
We are actually working on improving CPU usage for olm especially because of mobile devices! I hope to have some improvements in the next release.
@oschwartz10612 commented on GitHub (Jan 20, 2026):
Resolved by ba91478b89 will be in the next release shortly
<!-- gh-comment-id:3770586423 -->
@oschwartz10612 commented on GitHub (Jan 20, 2026):
Resolved by ba91478b89832990cb366e2362a21c93e5ce698e will be in the next release shortly
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @asardaes on GitHub (Jan 6, 2026).
Original GitHub issue: https://github.com/fosrl/olm/issues/73
Originally assigned to: @oschwartz10612 on GitHub.
Describe the Bug
I have a 4-core host running a Newt container and an Olm container. The Olm process continuously uses around 10% CPU, which is not extreme, but it's pretty much at the top of
top, which strikes me as odd. Newt stays below 1%.Environment
To Reproduce
Can't report much details as it is, this is the compose file I have to deploy Olm (I'm not using host network on purpose):
Besides the sensitive stuff, the JSON doesn't have anything out of the ordinary:
Expected Behavior
Less CPU usage, or at least a confirmation that more CPU usage is expected.
@oschwartz10612 commented on GitHub (Jan 8, 2026):
We are actually working on improving CPU usage for olm especially because of mobile devices! I hope to have some improvements in the next release.
@oschwartz10612 commented on GitHub (Jan 20, 2026):
Resolved by
ba91478b89will be in the next release shortly