User Tools

Site Tools


realtime:documentation:howto:debugging:cyclictest:test-design:threads

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
realtime:documentation:howto:debugging:cyclictest:test-design:threads [2018/07/23 09:58]
ebugden Add explanation for how many threads should be used
realtime:documentation:howto:debugging:cyclictest:test-design:threads [2018/07/23 12:37]
ebugden Improve phrasing
Line 1: Line 1:
 ====== Cyclictest - Number of measuring threads ====== ====== 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. ​+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 only have one measuring thread ​running on each 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.  ​+This option is also crucial for minimizing the effect that running Cyclictest has on the observed system. When using Cyclictestit 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 Cyclictest'​s ​measurements will be influenced by the latencies caused by its own measuring threads. The best way to make sure that only one measuring ​thread is supposed to execute at a given time is to have only one measuring thread executing on a given CPU.  ​