realtime:documentation:howto:debugging:cyclictest:faq
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
realtime:documentation:howto:debugging:cyclictest:faq [2018/07/24 09:32] ebugden [How does Cyclictest measure latencies?] Correct description of when cyclictest displays results |
realtime:documentation:howto:debugging:cyclictest:faq [2018/08/21 10:25] ebugden Move from temporary location to main tools page |
||
|---|---|---|---|
| Line 35: | Line 35: | ||
| ==== How can the influence of Cyclictest be minimized when evaluating latencies on an isolated set of CPUs? ==== | ==== How can the influence of Cyclictest be minimized when evaluating latencies on an isolated set of CPUs? ==== | ||
| - | When measuring the latencies on a subset of the CPUs, make sure that the main Cyclictest thread is running on the CPUs that are not being evaluated. For example, if a system has two CPUs and the latencies on CPU 0 are being evaluated, then the main Cyclictest thread should be pinned to CPU 1. Cyclictest's main thread is not real-time and it can potentially have an affect on the latencies that are measured if it executes on the evaluated CPUs. After starting Cyclictest, the main thread can be restricted to execution on a certain subset of CPUs using the [[realtime:documentation:howto:tools:cpu-partitioning:taskset|taskset]] command. For example, if the main thread's PID is 4764, then it can be pinned to CPU 1 using the following command: | + | When measuring the latencies on a subset of the CPUs, make sure that the main Cyclictest thread is running on the CPUs that are not being evaluated. For example, if a system has two CPUs and the latencies on CPU 0 are being evaluated, then the main Cyclictest thread should be pinned to CPU 1. Cyclictest's main thread is not real-time, but it can potentially have an affect on the latencies if it executes on the evaluated CPU(s) because there will be additional context switches. After starting Cyclictest, the main thread can be restricted to execution on a certain subset of CPUs using the [[realtime:documentation:howto:tools:cpu-partitioning:taskset|taskset]] command. For example, if the main thread's PID is 4764, then it can be pinned to CPU 1 using the following command: |
| <code bash> | <code bash> | ||
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
