# hotspot
**Repository Path**: brucewanght/hotspot
## Basic Information
- **Project Name**: hotspot
- **Description**: The Linux perf GUI for performance analysis.
- **Primary Language**: C++
- **License**: GPL-2.0
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No
## Statistics
- **Stars**: 0
- **Forks**: 0
- **Created**: 2020-05-31
- **Last Updated**: 2024-05-31
## Categories & Tags
**Categories**: Uncategorized
**Tags**: None
## README
# Hotspot - the Linux perf GUI for performance analysis
This project is a [KDAB](http://www.kdab.com) R&D effort to create a standalone
GUI for performance data. As the first goal, we want to provide a UI like
KCachegrind around Linux perf. Looking ahead, we intend to support various other
performance data formats under this umbrella.
## Table of Contents
- [Screenshots](#screenshots)
* [Visualize Data](#visualize-data)
* [Time Line](#time-line)
* [Record Data](#record-data)
- [Building Hotspot](#building-hotspot)
* [Required Dependencies](#required-dependencies)
* [On Debian/Ubuntu](#on-debianubuntu)
* [On Fedora](#on-fedora)
* [Arch Linux](#arch-linux)
* [OpenSUSE](#opensuse)
* [Building Hotspot itself](#building-hotspot-itself)
- [Getting Hotspot](#getting-hotspot)
* [ArchLinux](#archlinux)
* [For any Linux distro: AppImage](#for-any-linux-distro-appimage)
- [Using](#using)
* [Embedded Systems](#embedded-systems)
- [Known Issues](#known-issues)
* [Broken Backtraces](#broken-backtraces)
* [Missing Features](#missing-features)
* [Recording with perf without super user rights](#recording-with-perf-without-super-user-rights)
- [Qt Creator](#qt-creator)
- [License](#license)
## Screenshots
Here are some screenshots showing the most important features of hotspot in action:
### Visualize Data
The main feature of hotspot is visualizing a `perf.data` file graphically.
### Time Line
The time line allows filtering the results by time, process or thread. The data views will update accordingly.
### Record Data
You can also launch `perf` from hotspot, to profile a newly started application
or to attach to already running process(es). Do take the [caveats below](#recording-with-perf-without-super-user-rights)
into account though.
## Building Hotspot
### Required Dependencies
As of now, you will need the following dependencies to build this project:
- CMake 3.1.0 or higher
- any C++11 enabled compiler
- Qt 5.6.0 or higher
- libelf
- libelfutils
- gettext
- extra-cmake-modules
- KDE Frameworks 5 (packages are usually called libkf5-*-devel):
- threadweaver
- i18n
- configwidgets
- coreaddons
- itemviews
- itemmodels
- kio
- solid
- windowsystem
### On Debian/Ubuntu
```
add-apt-repository ppa:kubuntu-ppa/backports
apt-get update
apt-get install libkf5threadweaver-dev libkf5i18n-dev libkf5configwidgets-dev \
libkf5coreaddons-dev libkf5itemviews-dev libkf5itemmodels-dev libkf5kio-dev \
libkf5solid-dev libkf5windowsystem-dev libelf-dev libdw-dev cmake \
extra-cmake-modules gettext
```
### On Fedora
```
dnf install cmake gcc glibc-static gcc-c++ libstdc++-static qt5 qt5-devel \
extra-cmake-modules elfutils-devel kf5-threadweaver-devel kf5-ki18n-devel \
kf5-kconfigwidgets-devel kf5-kitemviews-devel kf5-kitemmodels-devel \
kf5-kio-devel kf5-solid-devel kf5-kwindowsystem-devel
```
### Arch Linux
```
pacman -Sy cmake gcc extra-cmake-modules threadweaver ki18n kconfigwidgets \
kitemviews kitemmodels kwindowsystem kio solid libelf gettext qt5-base
```
### OpenSUSE
```
zypper in cmake gcc-c++ extra-cmake-modules threadweaver-devel ki18n-devel kio-devel \
solid-devel kcoreaddons-devel threadweaver-devel kconfigwidgets-devel \
kitemmodels-devel kitemviews-devel kwindowsystem-devel \
libqt5-qtbase-devel libelf-devel libdw-devel gettext glibc-devel-static
```
### Building Hotspot itself
```
git clone --recurse-submodules https://github.com/KDAB/hotspot.git
mkdir build-hotspot
cd build-hotspot
cmake ../hotspot
make
# now you can run hotspot from the build folder:
./bin/hotspot
# or `make install` it and launch it from your $PATH
```
If you need help building this project for your platform, [contact us for help](https://www.kdab.com/about/contact/).
## Getting Hotspot
*Note: Hotspot is not packaged for most Linux distributions yet -- you'll likely have to resort to using the AppImage which will work on any recent Linux distro just fine*
### ArchLinux
hotspot is available in AUR (https://aur.archlinux.org/packages/hotspot).
### Gentoo
hotspot ebuilds are available from our overlay (https://github.com/KDAB/kdab-overlay).
### For any Linux distro: AppImage
Head over to our [download page](https://github.com/KDAB/hotspot/releases) and download the latest [AppImage](http://appimage.org/) release and just run it.
Command-line instructions:
```
wget https://github.com/KDAB/hotspot/releases/download/v1.1.0/hotspot-v1.1.0-x86_64.AppImage
chmod +x hotspot-v1.1.0-x86_64.AppImage
./hotspot-v1.1.0-x86_64.AppImage
```
*Note: Your system libraries or preferences are not altered. In case you'd like to remove Hotspot again, simply delete the downloaded file. Learn more about AppImage [here](http://appimage.org/).*
## Using
First of all, record some data with `perf`. To get backtraces, you will need to enable the dwarf callgraph mode:
```
perf record --call-graph dwarf
...
[ perf record: Woken up 58 times to write data ]
[ perf record: Captured and wrote 14.874 MB perf.data (1865 samples) ]
```
Now, if you have hotspot available on the same machine, all you need to do is launch it.
It will automatically open the `perf.data` file in the current directory (similar to `perf report`).
Alternatively, you can specify the path to the data file on the console:
```
hotspot /path/to/perf.data
```
### Embedded Systems
If you are recording on an embedded system, you will want to analyze the data on your
development machine with hotspot. To do so, make sure your sysroot contains the debug
information required for unwinding (see below). Then record the data on your embedded
system:
```
embedded$ perf record --call-graph dwarf
...
[ perf record: Woken up 58 times to write data ]
[ perf record: Captured and wrote 14.874 MB perf.data (1865 samples) ]
embedded$ cp /proc/kallsyms /tmp/kallsyms # make pseudo-file a real file
```
It's OK if your embedded machine is using a different platform than your host. On your
host, do the following steps then to analyze the data:
```
host$ scp embedded:perf.data embedded:/tmp/kallsyms .
host$ hotspot --sysroot /path/to/sysroot --kallsyms kallsyms \
perf.data
```
If you manually deployed an application from a path outside your sysroot, do this instead:
```
host$ hotspot --sysroot /path/to/sysroot --kallsyms kallsyms --appPath /path/to/app \
perf.data
```
If your application is also using libraries outside your sysroot and the appPath, do this:
```
host$ hotspot --sysroot /path/to/sysroot --kallsyms kallsyms --appPath /path/to/app \
--extraLibPaths /path/to/lib1:/path/to/lib2:... \
perf.data
```
And, worst-case, if you also use split debug files in non-standard locations, do this:
```
host$ hotspot --sysroot /path/to/sysroot --kallsyms kallsyms --appPath /path/to/app \
--extraLibPaths /path/to/lib1:/path/to/lib2:... \
--debugPaths /path/to/debug1:/path/to/debug2:... \
perf.data
```
## Known Issues
If anything breaks in the above and the output is less usable than `perf report`, please [report an issue on GitHub](https://github.com/KDAB/hotspot/issues).
That said, there are some known issues that people may trip over:
### Broken Backtraces
Unwinding the stack to produce a backtrace is a dark art and can go wrong in many ways.
Hotspot relies on `perfparser` (see below), which in turn relies on `libdw` from elfutils
to unwind the stack. This works quite well most of the time, but still can go wrong. Most
notably, unwinding will fail when:
- an ELF file (i.e. executable or library) referenced by the `perf.data` file is missing
- to fix this, try to use one of the following CLI arguments to let hotspot know where to look for the ELF files:
- `--debugPaths `: Use this when you have split debug files in non-standard locations
- `--extraLibPaths `: Use this when you have moved libraries to some other location since recording
- `--appPath `: This is kind of a combination of the above two fields. The path is traversed recursively, looking for debug files and libraries.
- `--sysroot `: Use this when you try to inspect a data file recorded on an embedded platform
- an ELF file is missing debug information
- to fix this, install the debug package from your distro
- or compile the code in "release with debug" mode, i.e. ensure your compiler is invoked with something like `-O2 -g`. You will have to repeat the `perf record` step
- potentially both of the above is not an option for you, e.g. when the library is closed source and supplied by a thirdparty vendor. If that is the case,
you may be lucky and the library contains frame pointers. If so, then try to build elfutils from current git master (you want commit a55df2c1, which should be part of 0.170).
This version of elfutils will try to fallback to the frame pointer for unwinding, when the debug information is missing.
- your call stacks are too deep
- by default, `perf record` only copies a part of the stack to the data file. This can lead to issues with very deep call stacks, which will be cut off at some point.
This issue will break the top-down call trees in hotspot, as visualized in the Top-Down view or the Flame Graph. To fix this, you can try to increase the stack dump size, i.e.:
perf record --call-graph dwarf,32768
Note that this can dramatically increase the size of the `perf.data` files - use it with care. Also have a look at `man perf record`.
- For some scenarios, recursive function calls simply fail to be unwound. See also https://github.com/KDAB/hotspot/issues/93
### Missing Features
Compared to `perf report`, hotspot misses a lot of features. Some of these are planned to be resolved
in the future. Others may potentially never get implemented. But be aware that the following features
are _not_ available in hotspot currently:
- tracepoints: we only analyze and show samples. This means that it is currently impossible to do off-CPU profiling with hotspot.
- annotate: the caller/callee view shows cost attributed to individual source lines. But a proper annotation view like `perf annotate`, esp. on the instruction level, is currently missing.
- the columns in the tables are currently hardcoded, while potentially a user may want to change this to show e.g. cost per-process or thread and so forth
- many of the more advanced features, such as `--itrace`, `--mem-mode`, `--branch-stack` and `--branch-history`, are unsupported
### Recording with perf without super user rights
It is **not** a good idea to launch hotspot with `sudo` or as `root` user. See e.g.
[Editing Files As Root](https://blog.martin-graesslin.com/blog/2017/02/editing-files-as-root/)
for an article on that matter. [Issue #83](https://github.com/KDAB/hotspot/issues/83) is
also relevant in this contact.
But without superuser rights, you may see error messages such as the following
when using hotspot's record feature:
You may not have permission to collect stats.
Consider tweaking /proc/sys/kernel/perf_event_paranoid:
-1 - Not paranoid at all
0 - Disallow raw tracepoint access for unpriv
1 - Disallow cpu events for unpriv
2 - Disallow kernel profiling for unpriv
To workaround this limitation, hotspot can temporarily elevate the perf privileges.
This is achieved by applying [these steps](https://superuser.com/questions/980632/run-perf-without-root-right),
bundled into [a script](scripts/elevate_perf_privileges.sh) that is run via `kdesudo` or `kdesu`.
The resulting elevated privileges are also required for kernel tracing in general and Off-CPU profiling in particular.
## Qt Creator
This project leverages the excellent `perfparser` utility created by The Qt Company
for their Qt Creator IDE. If you are already using Qt Creator, consider leveraging
its integrated [CPU Usage Analyzer](http://doc.qt.io/qtcreator/creator-cpu-usage-analyzer.html).
## License
Hotspot is dual-licensed under the GPL v2+ or under a commercial KDAB license.
See [LICENSE.GPL.txt](LICENSE.GPL.txt), [LICENSE.txt](LICENSE.txt) and [LICENSE.US.txt](LICENSE.US.txt)
for more information, or contact info@kdab.com if any conditions of this licensing are not clear to you.