This repo contains various Linux and Android Performance Analysis tools built with the Microsoft Performance Toolkit SDK.

Tools are built with open source .NET Core and can be run on the cmd-line or in the WPA GUI. All the logs that are supported are open source.

Not only are the raw logs parsed, but a lot of smart post processing / correlation is done to make your life easier as a perf analyst. We hope you can solve & debug tough issues on you or your customers systems with this toolset!

Tracing supported:

• LTTng (Kernel CPU scheduling, Processes, Threads, Block IO/Disk, Syscalls, File events, etc)
• perf CPU Sampling(cpu-clock)
• Perfetto Android & Chromium (CPU Scheduling, CPU Sampling, CPU Frequency, FTrace, Android Logs, Generic Events / Default Tracks, GPU Counters, Jank Detection, Processes, Android Packages)

Logs supported:

• Dmesg
• Cloud-Init
• WaLinuxAgent
• AndroidLogcat

Optional WPA GUI:

If you want to see a demo or get more in-depth info on using these tools (LTTng) check out a talk given at the Linux Tracing Summit:

Linux & Windows Perf Analysis using WPA (LTTng), (slides) (video)

Featuring some use-cases and some walkthroughs

• New tools for analyzing Android, Linux, and Chromium browser performance – Microsoft-Performance-Tools for Linux-Android
• Perfetto tooling for analyzing Android, Linux, and Chromium browser performance – Microsoft-Performance-Tools-Linux-Android
• New Android logcat support available in Microsoft Performance Tools for Linux & Android

• .NET Core Runtime 3.1.x

• .NET Core SDK 3.1.x
• Visual Studio, VSCode, or your favorite editor!

• For plugins Download see Releases

• NuGet Pkgs see PerformanceToolkitPlugins

• (Windows Only GUI - Install) Using the WPA GUI to load these tools as plugins

  • Download the latest Store Windows Performance Analyzer (Preview)

The tools can be run in several modes:

• Cross-platform with .NET Core (Any OS that .NET Core supports)
  • Used as a library to process traces / logs programatically in a .NET Core language like C#
    • Examples:
    • LTTng 1, LTTng 2
    • Perf
    • LinuxLogs
    • Perfetto
  • With a driver program for example dumping to screen or text format
    • ./LTTngDriver.exe LTTngKernelTraceFolder
    • ./LTTngDriver.exe LTTng-Kernel-Trace.ctf (trace folder is zipped and renamed to .ctf)
• (Windows Only - Run) Using the WPA GUI to load these tools as plugins
  • WPA needs to be told where to find these additional plugins.
  • Using Windows Launcher script

    .\LaunchWpaPerfToolsLinuxAndroid.ps1 -i c:\PATH\TO\lttng-kernel-trace.ctf

    • -LinuxPerfToolsPluginFolder path may need to be specified if not auto-found correctly
  • In Command Prompt with -addsearchdir and -i trace file:

      wpa.exe -addsearchdir %HOMEDRIVE%%HOMEPATH%\Downloads\Microsoft-Performance-Tools-Linux-Android-1.2\Microsoft-Performance-Tools-Linux-Android\MicrosoftPerfToolkitAddins -i c:\PATH\TO\lttng-kernel-trace.ctf
    

  • OR with Env Variable to pick file from UI

     SET WPA_ADDITIONAL_SEARCH_DIRECTORIES=%HOMEDRIVE%%HOMEPATH%\Downloads\Microsoft-Performance-Tools-Linux-Android-1.2\Microsoft-Performance-Tools-Linux-Android\MicrosoftPerfToolkitAddins
     wpa.exe
    

  • Optional Troubleshooting - Verify that this WPA version supports plugins
    • In Command Prompt - Example:

      wpa.exe /?
      "C:\Program Files\WindowsApps\Microsoft.WindowsPerformanceAnalyzerPreview_10.0.22504.0_x64__8wekyb3d8bbwe\10\Windows Performance Toolkit\wpa.exe" /?
      

    • Verify that these 2 command line WPA options are supported:
      • OPTIONS: -addsearchdir PATH. Adds a directory path to the plugin search path. ....
      • ENVIRONMENT VARIABLES: WPA_ADDITIONAL_SEARCH_DIRECTORIES - A semicolon (;) delimited list of additional directories to search for plugins. Equivalent to the -addsearchdir option.
• (Windows) Command-line dumping to a text format based on the WPA UI (say CSV) (wpaexporter.exe)

  "C:\Program Files\WindowsApps\Microsoft.WindowsPerformanceAnalyzerPreview_10.0.22504.0_x64__8wekyb3d8bbwe\10\Windows Performance Toolkit\wpaexporter.exe" -addsearchdir PLUGIN_FOLDER -i traceFile
  

• Linux
  • Please see Linux Trace Log Capture
• Perfetto
  • Android - Please see Record traces on Android
  • Linux - Please see Record traces on Linux
  • Chromium - In chrome://tracing/ Record choose "Use protobuf" OR use UI at https://ui.perfetto.dev/
    • Also see https://www.chromium.org/developers/how-tos/trace-event-profiling-tool/recording-tracing-runs

• LTTng - If you just need to open only a LTTng trace by itself in folder format
  • WPA -> Open -> Folder -> (Select CTF folder)
    • Note: Requires >= 1.2 release AND WPA >= 10.6.20.1 (via WPA Help -> About)
• Perfetto
  • WPA -> Open -> (Select Perfetto trace file)
    • Note: The Perfetto plugin explicitly supports the .perfetto-trace and .pftrace file types, but it does support more (e.g. Protobuf, Chrome JSON). You just need to rename to one of the stated supported types
• Unified (LTTng, Perfetto, or other multiple different logs files together)
  • Once you gather the data, there is a tiny bit of prep needed to open them in a single unified timeline (like the screenshot above)
  • If you want to open multiple logs together in single timeline - Copy all trace files and logs you want to open to single folder
  • Example: You want to open in the same timeline: LTTng, Perf CPU Sampling, Dmesg
    • Ensure that the Linux CTF folder/trace is zipped and renamed to .ctf in the same folder (hack so open Unified works)
  • WPA -> File -> Open -> Multi-select all files and choose "Open Unified"

If you want to learn how to use the GUI UI in general see WPA MSDN Docs

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.