realtime:documentation:howto:debugging:cyclictest:start
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:start [2018/07/16 14:35] ebugden Explain cyclictest use cases |
— (current) | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Cyclictest ====== | ||
| - | Cyclictest accurately and repeatedly measures the difference between a thread's intended wake-up time and the time at which it actually wakes up in order to provide statistics about the system's latencies. It can measure latencies in real-time systems caused by the hardware, the firmware, and the operating system. Some of the most common uses for Cyclictest are described below. | ||
| - | |||
| - | The original test was written by Thomas Gleixner (tglx), but several people have subsequently contributed modifications. Cyclictest is currently maintained by Clark Williams and John Kacur and is part of the test suite [[realtime:documentation:howto:tools:rt-tests|rt-tests]]. | ||
| - | |||
| - | <WRAP rightalign>[[realtime:documentation:howto:debugging:cyclictest:details|Read more about how to use Cyclictest]]</WRAP> | ||
| - | |||
| - | ---- | ||
| - | |||
| - | <WRAP half column> | ||
| - | ===== System Benchmarking ===== | ||
| - | |||
| - | Cyclictest is most commonly used as a standardized test for evaluating the relative performance of real-time systems. | ||
| - | |||
| - | OSADL (Open Source Automation Development Lab) uses Cyclictest to continuously monitor the latencies of several systems. More details about the project and about the specific Cyclictest options they use can be found on the [[https://www.osadl.org/Continuous-latency-monitoring.qa-farm-monitoring.0.html|OSADL website]]. | ||
| - | |||
| - | </WRAP> | ||
| - | |||
| - | <WRAP half column> | ||
| - | ===== Latency Debugging ===== | ||
| - | |||
| - | Cyclictest can be used to help identify certain system latencies and what is causing them. Its many program options allow the test to be configured for measuring very specific latencies. | ||
| - | |||
| - | Once a latency has been identified, Cyclictest can be used to produce relevant traces that can help determine the source of the latency. These traces can be taken using different Ftrace tracers in order to control the level of detail in the traces and the tracing overhead. | ||
| - | |||
| - | <WRAP rightalign>[[realtime:documentation:howto:debugging:cyclictest:debugging|Read more about latency debugging]]</WRAP> | ||
| - | |||
| - | </WRAP> | ||
| - | |||
| - | <WRAP half column> | ||
| - | ===== Approximation of Application Performance ===== | ||
| - | |||
| - | Cyclictest is not intented for measuring the latencies of applications running on real-time systems. However, in some cases it can be used to get a rough estimate of an RT application or task's response time. | ||
| - | |||
| - | <WRAP rightalign>[[realtime:documentation:howto:debugging:cyclictest:app-performance|Read more about approximating application performance]]</WRAP> | ||
| - | |||
| - | </WRAP> | ||
realtime/documentation/howto/debugging/cyclictest/start.1531751713.txt.gz ยท Last modified: 2018/07/16 14:35 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
