realtime:documentation:howto:tools:cyclictest:app-performance
Differences
This shows you the differences between two versions of the page.
|
realtime:documentation:howto:tools:cyclictest:app-performance [2018/08/21 09:40] ebugden Moved from temporary location to main tools page |
realtime:documentation:howto:tools:cyclictest:app-performance [2018/08/21 10:55] (current) ebugden [Latency Approximation] Update link |
||
|---|---|---|---|
| Line 13: | Line 13: | ||
| Approximating application latencies requires two different runs of Cyclictest, one to establish a baseline performance and a second to determine how the baseline changes with the influence of the application or task. After these two tests have been completed, the approximate maximum latency of the application or task can then be determined by calculating the difference between these two results. The baseline is determined by running Cyclictest with a priority that is higher than the task or application whose performance is to be measured. The value influenced by the application or task is measured by giving Cyclictest a priority that is slightly lower than the evaluated application or task. | Approximating application latencies requires two different runs of Cyclictest, one to establish a baseline performance and a second to determine how the baseline changes with the influence of the application or task. After these two tests have been completed, the approximate maximum latency of the application or task can then be determined by calculating the difference between these two results. The baseline is determined by running Cyclictest with a priority that is higher than the task or application whose performance is to be measured. The value influenced by the application or task is measured by giving Cyclictest a priority that is slightly lower than the evaluated application or task. | ||
| - | Application latency approximation using Cyclictest is similar to measuring system latencies. Most of the principles explained on the Cyclictest test design page about choosing [[realtime:documentation:howto:debugging:cyclictest:test-design:start#option-selection|program options]] still apply here and these pages can be read to help determine which options are appropriate for the test situation. | + | Application latency approximation using Cyclictest is similar to measuring system latencies. Most of the principles explained on the Cyclictest test design page about choosing [[realtime:documentation:howto:tools:cyclictest:test-design#option-selection|program options]] still apply here and these pages can be read to help determine which options are appropriate for the test situation. |
| Because there are so many factors involved in generating the latencies, it is particularly important to run the tests as long as possible when approximating application performance. | Because there are so many factors involved in generating the latencies, it is particularly important to run the tests as long as possible when approximating application performance. | ||
realtime/documentation/howto/tools/cyclictest/app-performance.1534844439.txt.gz ยท Last modified: 2018/08/21 09:40 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
