Inaccurate Core Count in Server Stats #405

New Issue

GiteaMirror · 2025-10-31T15:10:59-05:00

GiteaMirror commented

2025-10-31 15:10:59 -05:00

Originally created by @syphernl on GitHub (Jun 2, 2025).

Under Servers => Server => Stats, the reported core count is incorrect.
All Komodo servers (LXC containers) are assigned 6 cores, confirmed via cat /proc/cpuinfo, but the UI inconsistently displays 4, 5, or 6 cores across servers while they all are supposed to be showing 6.

Running Komodo 1.18.0

Originally created by @syphernl on GitHub (Jun 2, 2025). Under Servers => Server => Stats, the reported core count is incorrect. All Komodo servers (LXC containers) are assigned 6 cores, confirmed via cat /proc/cpuinfo, but the UI inconsistently displays 4, 5, or 6 cores across servers while they all are supposed to be showing 6. Running Komodo 1.18.0

GiteaMirror added the

seen 👀

label 2025-10-31 15:10:59 -05:00

GiteaMirror commented

2025-10-31 15:10:59 -05:00

@SCUR0 commented on GitHub (Jun 3, 2025):

I'm seeing this as well except I have no core limit set with the host having four cores and but the server status is showing 2.

admin@docker:~$ sudo docker inspect --format='{{.HostConfig.NanoCpus}}' komodo-periphery-1
0

@SCUR0 commented on GitHub (Jun 3, 2025): I'm seeing this as well except I have no core limit set with the host having four cores and but the server status is showing 2. ``` admin@docker:~$ sudo docker inspect --format='{{.HostConfig.NanoCpus}}' komodo-periphery-1 0 ```

GiteaMirror commented

2025-10-31 15:10:59 -05:00

@mbecker20 commented on GitHub (Jun 7, 2025):

Komodo periphery uses the sysinfo rust crate for core count, the periphery code getting it is here and it is directly mapped from the sysinfo method: 4d401d7f20/bin/periphery/src/stats.rs (L198).

You can open an issue with sysinfo crate regarding this issue. You should provide detailed system information including whether running in VM / LXC / container / native, etc.

@mbecker20 commented on GitHub (Jun 7, 2025): Komodo periphery uses the [sysinfo](https://github.com/GuillaumeGomez/sysinfo) rust crate for core count, the periphery code getting it is here and it is directly mapped from the sysinfo method: https://github.com/moghtech/komodo/blob/4d401d7f200fd56d091b9ad4489f1e84f9aeb223/bin/periphery/src/stats.rs#L198. You can open an issue with sysinfo crate regarding this issue. You should provide detailed system information including whether running in VM / LXC / container / native, etc.

GiteaMirror commented

2025-10-31 15:11:00 -05:00

@kenneth-church commented on GitHub (Aug 28, 2025):

Could this perhaps be an issue with the difference between physical and logical cores?
Mentioned in this sysinfo issue.

@kenneth-church commented on GitHub (Aug 28, 2025): Could this perhaps be an issue with the difference between physical and logical cores? Mentioned in this [sysinfo](https://github.com/GuillaumeGomez/sysinfo/issues/1142) issue.

GiteaMirror commented

2025-10-31 15:11:00 -05:00

@arifroni commented on GitHub (Oct 23, 2025):

i see similar issue as well. i have several lxcs. most of them have 2 cores, these are shown accurately in komodo. one of the them have 1, thats also correct in komodo. 2 lxcs have 4 cores each, in komodo it shows 3.

@arifroni commented on GitHub (Oct 23, 2025): i see similar issue as well. i have several lxcs. most of them have 2 cores, these are shown accurately in komodo. one of the them have 1, thats also correct in komodo. 2 lxcs have 4 cores each, in komodo it shows 3.

GiteaMirror commented

2025-10-31 15:11:01 -05:00

@PAS-BC commented on GitHub (Oct 30, 2025):

Only just started my Komodo journey.
Added Periphery as a systemd entity to an LXC and added the new Server.
Komodo identified the single core as overstretched, so I increased the Core Resources to 2 from the Proxmox GUI.
Stopped and restarted the LXC - both from Proxmox and again within Komodo
Refreshed Komodo Server Stats page
Core Count still showing as '1 Core'

Edit:
As a quick test, I increased the Memory allocation from 1 GiB to 2 GiB and rebooted LXC
Komodo picked up the RAM change correctly

@PAS-BC commented on GitHub (Oct 30, 2025): Only just started my Komodo journey. Added Periphery as a systemd entity to an LXC and added the new Server. Komodo identified the single core as overstretched, so I increased the Core Resources to 2 from the Proxmox GUI. Stopped and restarted the LXC - both from Proxmox and again within Komodo Refreshed Komodo Server Stats page Core Count still showing as '1 Core' Edit: As a quick test, I increased the Memory allocation from 1 GiB to 2 GiB and rebooted LXC Komodo picked up the RAM change correctly

GiteaMirror referenced this issue

2025-10-31 15:20:09 -05:00

[PR #383] [MERGED] 1.17.1 #728

GiteaMirror referenced this issue

2025-10-31 15:20:20 -05:00

[PR #405] [MERGED] Make listener address configurable & Add support for IPv6 #734

Sign in to join this conversation.