realtime:documentation:howto:debugging:cyclictest:test-design:start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
realtime:documentation:howto:debugging:cyclictest:test-design:start [2018/08/06 13:15] ebugden [Cyclictest - Test Design] Add links to results and how cyclictest works |
realtime:documentation:howto:debugging:cyclictest:test-design:start [2018/08/06 13:16] ebugden [Cyclictest - Test Design] Add line to separate introduction from content |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| When learning how to design a test, it is useful to have a look at [[realtime:documentation:howto:debugging:cyclictest:result-examples|examples of results]] that show the effect of different loads and parameters on the latencies measured by Cyclictest. It is also important to understand [[realtime:documentation:howto:debugging:cyclictest:start#technical-explanation|how Cyclictest works]] before reading the rest of the content on this page. | When learning how to design a test, it is useful to have a look at [[realtime:documentation:howto:debugging:cyclictest:result-examples|examples of results]] that show the effect of different loads and parameters on the latencies measured by Cyclictest. It is also important to understand [[realtime:documentation:howto:debugging:cyclictest:start#technical-explanation|how Cyclictest works]] before reading the rest of the content on this page. | ||
| + | |||
| + | ---- | ||
| Cyclictest measures the latencies that occur in the one particular situation for which it is configured. In other words, running Cyclictest once will not identify all the possible latencies in all possible situations on a system. If Cyclictest is being used to debug a latency, the options should be chosen with the goal of observing that latency. However, if Cyclictest is being used to globally evaluate a system's performance, then many different runs of Cyclictest with different parameters are required. | Cyclictest measures the latencies that occur in the one particular situation for which it is configured. In other words, running Cyclictest once will not identify all the possible latencies in all possible situations on a system. If Cyclictest is being used to debug a latency, the options should be chosen with the goal of observing that latency. However, if Cyclictest is being used to globally evaluate a system's performance, then many different runs of Cyclictest with different parameters are required. | ||
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
