Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Trace Compass/News/NewIn20"

Line 38: Line 38:
  
 
[[Image:CriticalPathView.png]]
 
[[Image:CriticalPathView.png]]
 +
 +
= Virtual CPU view =
 +
To better understand what is happening in such a virtual environment, it is necessary to trace all the machines involved, guests and hosts, and correlate this information in an experiment that will display a complete view of the virtualized environment. The '''Virtual CPU''' view has been added for that.
 +
 +
In order to be able to correlate data from the guests and hosts traces, each hypervisor supported by Trace Compass requires some specific events, that are sometimes not available in the default installation of the tracer. For QEMU/KVM special LTTng kernel modules exist which need to be installed on the traced system. For more information, please follow the instructions in the Trace Compass user guide.
 +
 +
[[Image:VirtualCPUView.png]]
  
 
= Bookmarks and custom markers =
 
= Bookmarks and custom markers =

Revision as of 14:00, 18 January 2016

Pie charts in Statistics view

Pie Charts have been added to the Statistics view.

StatisticsWithPieCharts.png

Gridlines in Time Graph views

Grid lines have been added to the time graph views such as the Control Flow view.

InitialGridLineSupport.png

System call latency analysis

For analyzing of analyzing system call latencies in the Linux Kernel using LTTng kernel traces, the System Call Latency Analysis has been added. Various views will now display the results of the analysis in different ways.

System call latency table

The System Call Latency table lists all latencies occurred per system call type occurred within the currently open trace.

SysCallLatencyAnalysis.png

System call latency scatter graph

The System Call Latency vs Time view visualizes system call latencies in the Linux Kernel over time.

SyscallLatencyScatterChart.png

System call latency statistics

The System Call Latency Statistics view shows statistics about system call latencies. I lists the minimum, maximum and average latency as well as the standard deviation for a given system call type.

SystemCallStatistics.png

System call latency density

The System Call Density view shows the distribution of the latencies for the current selected time window of the traces.

SystemCallDensity.png

Critical flow view

A critical flow analysis and view has been added to show dependency chains for a given process.

CriticalPathView.png

Virtual CPU view

To better understand what is happening in such a virtual environment, it is necessary to trace all the machines involved, guests and hosts, and correlate this information in an experiment that will display a complete view of the virtualized environment. The Virtual CPU view has been added for that.

In order to be able to correlate data from the guests and hosts traces, each hypervisor supported by Trace Compass requires some specific events, that are sometimes not available in the default installation of the tracer. For QEMU/KVM special LTTng kernel modules exist which need to be installed on the traced system. For more information, please follow the instructions in the Trace Compass user guide.

VirtualCPUView.png

Bookmarks and custom markers

Support for user bookmarks in time graph views

It is now possible to create bookmarks in time graph view for a single or time range selection. This will allow users to annotate their traces and easily navigate to region of interests.

UserDefinedMarkers.png

Lost event markers in time graph views

Time graph views such as Control Flow or Resources view now highlight the durations where lost lost events occurred. .

LostEventMarkers.png

Navigation for trace markers in Time Graph Views

It is possible to navigate from one marker forward and backwards in time graph views as well as it's possible to configure which marker type to include for the navigation. It is also possible to hide markers of a given type from the view menu.

NavigationOfMarkers.png

API for trace specific markers

A new API is provided to define programmatically trace specific markers. This can be used, for example, to visualize time periods in the time graph views.

Display of soft IRQ names in the Resources view

The Resources view now displays the soft IRQ names together with the Soft IRQ numbers.

ResourcesViewSoftIRQNames.png

Bugs fixed in this release

See Bugzilla report Bugs Fixed in Trace Compass 2.0

Back to the top