github-starred/olm
2
0
Fork 0
mirror of https://github.com/fosrl/olm.git synced 2026-05-06 10:47:55 -05:00
Code Issues 61 Packages Projects Releases 15 Wiki Activity

[GH-ISSUE #73] CPU Usage #137

New Issue
Closed
opened 2026-04-16 07:40:52 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-16 07:40:52 -05:00
Owner
Copy Link

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):

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:

{
  "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.

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.
GiteaMirror added the enhancement label 2026-04-16 07:40:52 -05:00
GiteaMirror commented 2026-04-16 07:40:53 -05:00
Author
Owner
Copy Link

@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.
GiteaMirror commented 2026-04-16 07:40:54 -05:00
Author
Owner
Copy Link

@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
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
dependencies
documentation
enhancement
good first issue
help wanted
needs investigating
pull-request
Mirrored from GitHub Pull Request
 stale
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/olm#137
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?