Hi all. cpupower utility was helpful in setting governor to 'performance' mode in Debian, which appears to help stabilize/lower cyclictest numbers, even while under stress-ng loads. Any tips for debugging outliers? I mean to say, debugging a missed latency target, by tracing kernel to find the cause?
Hello Codesys Community, When searching for term 'rt_preempt' there are past questions on the topic of reducing jitter on the Codesys Linux runtime, running on a Debian-based OS. I found these suggestions: Use of the RT_PREEMPT kernel patch Ensure stable CPU clock Use of CyclicTest tool for diagnostics To further improve performance (reduce jitter), are there additional suggestions from Codesys or the others in the community? For example: Debugging kernel latency Building a smaller/"lighter" kernel...
Hello Codesys Community, When searching for term 'rt_preempt' there are past questions on the topic of reducing jitter on the Codesys Linux runtime, running on a Debian-based OS. I found these suggestions: Use of the RT_PREEMPT kernel patch Ensure stable CPU clock * Use of CyclicTest tool for diagnostics To further improve performance (reduce jitter), are there additional suggestions from Codesys or the others in the community? For example: Debugging kernel latency Building a smaller/"lighter" kernel...