Skip to content

Commit

Permalink
Add user documentation for SWS Latency analysis
Browse files Browse the repository at this point in the history
This commit adds user documentation for SWS Latency analysis. It
explains the purpose of the SWS Latency analysis and usage of the new
Priority/Thread name statistics view.

[Added] User guide for SWS Latency analysis

Change-Id: I05c1778249a307e7141a08aa45d05f816f158c1b
Signed-off-by: Hoang Thuan Pham <hoang.pham@calian.ca>
Reviewed-on: https://git.eclipse.org/r/c/tracecompass/org.eclipse.tracecompass/+/204271
Tested-by: Trace Compass Bot <tracecompass-bot@eclipse.org>
Tested-by: Matthew Khouzam <matthew.khouzam@ericsson.com>
Reviewed-by: Patrick Tasse <patrick.tasse@gmail.com>
Reviewed-by: Matthew Khouzam <matthew.khouzam@ericsson.com>
  • Loading branch information
hoangphamEclipse authored and PatrickTasse committed Oct 13, 2023
1 parent 501cd49 commit 2eeea8d
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 0 deletions.
Expand Up @@ -2926,6 +2926,14 @@ The LTTng Kernel Events editor '''is''' the plain TMF [[#Events_Editor | Events
[[Image:images/LTTng2EventsEditor.png]]
== Scheduler wake up/Scheduler switch Latency Analysis ==
The '''Scheduler wake up/Scheduler switch Latency Analysis''' measures the latency between the sched_wakeup (scheduler wake up) and sched_switch (scheduler switch) event. In layman's terms, the analysis measures the time from the moment a process/thread wakes up until it is switched onto the CPU. The durations are visualized using the '''Latency''' views. For more information about the '''Latency''' views see chapter [[#Latency_Analyses | Latency Analyses]].
Besides the typical latency views, the analysis also provides a Priority/Thread name Statistics view. The view groups latencies using thread names and priorities, and provides statistics for these groups.
[[Image:images/swslatency/PriorityThreadnameView.png| Priority/Thread name Statistics view]]
= LTTng-UST Analyses =
The Userspace traces are taken on an application level. With kernel traces, you know what events you will have as the domain is known and cloistered. Userspace traces can contain pretty much anything. Some analyses are offered if certain events are enabled.
Expand Down
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 2eeea8d

Please sign in to comment.