DGS (General)takahiro.yamamoto - 17:37 Tuesday 20 January 2026 (36182)
Print this reportHardware replacement of k1cam2This was yesterday's work.
k1cam2 had been installed as a tertiary and a new version of GigE camera server (klog#33113. But the previous hardware was poor CPU power and it wasn't able to operate only 3 GigE cameras (larger than as 12 CPU load for 6C/6T). So I replaced k1cam2 hardware in this time as a new and a more powerful one (8C/16T).
k1cam2 with the new hardware can operate 3 GigE cameras with ~5 as CPU load for 8C/16T. Though the situation was improved, it's not enough to move all GigE cameras to k1cam2. After this work, I noticed CPU cores are running as ~0.8-1.2GHz. On the other hand, this CPU should work 3.2GHz according to the specification sheet. So we need to check BIOS settings of power saving mode. This work will be done in next Thursday.
Comments to this report:
takahiro.yamamoto - 16:31 Thursday 22 January 2026 (36196)
Print this reportI set CPU performance/power efficiency via OS function because there is no settings to anchor it on BIOS. Now CPU load of k1cam2 is less than 1.0 (8C/16T) with 3 Cameras. In theory, k1cam2's CPU should be able to handle all cameras (though another limitation will likely appear first).
----- On legacy hardware, there was settings to anchor CPU behavior as "Max Performance" on BIOS. I tried to use it on the new hardware at first but there was not. Only a setting is to allow to control CPU behavior via OS or not. And also, if it's set as "Not allowed", CPU always works as "balance Performance/Efficiency". I'm not sure why CPU continued to work ~1GHz even though each camera-server process uses several hundreds percent. Anyway in "balanced mode", CPU didn't work with the rated value for camera server processes.
Next, I tried to control it via OS functions. A way to disable intel_pstate by kernel parameter via grub didn't work. On the other hand, manual rewriting /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor and /sys/devices/system/cpu/cpu*/cpufreq/energy_performance_preference as "performance" works fine to anchor the operational clock as the rated value. So I installed "linux-cpupower" packages and made a new systemd service to anchor the CPU behavior at the beginning of OS launching (see also JGW-T2516613).
After deploying these settings, CPU stably works with the rated value even after rebooting OS. Current CPU load with 3 GigE camera is less than 1.0 (8C/16T). So all cameras can be handled only by CPU resources of k1cam2 in theory. Next step is to move cameras on k1cam0/k1cam1 to k1cam2 and to upgrade k1cam0 and k1cam1.