realtime:documentation:howto:debugging:cyclictest:test-design:threads
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:test-design:threads [2018/07/23 09:58] ebugden Add explanation for how many threads should be used |
— (current) | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Cyclictest - Number of measuring threads ====== | ||
| - | The threads option (--threads) is used to specify the number of measuring threads that will be used by Cyclictest when detecting latencies. In general, it is a good idea to have one measuring thread per CPU on the system. | ||
| - | |||
| - | This option is also crucial for minimizing the effect that running Cyclictest has on the observed system. When running Cyclictest it is important make sure that only one measuring thread is intended to execute at any given time. If the intended execution times of two or more Cyclictest threads overlap then the Cyclictest measurements will be influenced by the latencies caused by its own measuring threads. The best way to make sure that only one Cyclictest thread is supposed to execute at a given time is to have only one measuring thread executing on a CPU. | ||
realtime/documentation/howto/debugging/cyclictest/test-design/threads.1532339914.txt.gz ยท Last modified: 2018/07/23 09:58 by ebugden
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
