2016-12-04 19:18:38 +03:00
# easy_profiler [![version](https://img.shields.io/badge/version-1.0.0%20beta-009688.svg)](https://github.com/yse/easy_profiler/releases)
2016-11-13 17:34:19 +03:00
[![Build Status ](https://travis-ci.org/yse/easy_profiler.svg?branch=develop )](https://travis-ci.org/yse/easy_profiler)
2016-11-13 16:31:27 +03:00
[![License ](https://img.shields.io/badge/License-Apache%202.0-blue.svg )](https://www.apache.org/licenses/LICENSE-2.0)
[![License: GPL v3 ](https://img.shields.io/badge/License-GPL%20v3-blue.svg )](http://www.gnu.org/licenses/gpl-3.0)
2016-08-31 22:47:17 +03:00
1. [About ](#about )
2016-09-26 22:00:22 +03:00
2. [Usage ](#usage )
3. [Build ](#build )
2016-08-31 22:47:17 +03:00
- [Linux ](#linux )
- [Windows ](#windows )
# About
2016-09-26 22:00:22 +03:00
Lightweight cross-platform profiler library for c++
2016-06-29 06:47:50 +04:00
2016-09-15 00:08:53 +03:00
You can profile any function in you code. Furthermore this library provide measuring time of any block of code.
2016-09-15 00:33:47 +03:00
For example, information for 12 millions of blocks is using less than 300Mb of memory.
Working profiler slows your application execution for only 1-2%.
Disabled profiler will not affect your application execution in any way. You can leave it in your Release build
2016-11-13 15:54:06 +03:00
and enable it at run-time at any moment during application launch to see what is happening at the moment.
2016-09-15 00:33:47 +03:00
Also the library can capture system's context switch events between threads. Context switch information includes
duration, target thread id, thread owner process id, thread owner process name.
2016-09-15 00:08:53 +03:00
You can see the results of measuring in simple GUI application which provides full statistics and renders beautiful time-line.
2016-06-29 06:47:50 +04:00
2016-11-06 17:05:53 +03:00
![GUI screenshot ](https://cloud.githubusercontent.com/assets/10530007/20060202/0eb687de-a50b-11e6-8075-5adb951943db.png )
2016-11-05 19:24:12 +03:00
2016-08-31 22:47:17 +03:00
# Usage
2016-09-30 00:12:36 +04:00
First of all you can specify path to include directory which contains `include/profiler` directory and define macro `BUILD_WITH_EASY_PROFILER` .
2016-09-15 00:08:53 +03:00
For linking with easy_profiler you can specify path to library.
2016-08-31 22:47:17 +03:00
2016-06-29 06:47:50 +04:00
Example of usage.
2016-09-15 00:08:53 +03:00
This code snippet will generate block with function name and Magenta color:
2016-06-29 06:47:50 +04:00
```cpp
2016-10-21 22:21:25 +03:00
#include <easy/profiler.h>
2016-08-31 22:47:17 +03:00
2016-09-15 00:08:53 +03:00
void frame() {
2016-09-15 00:33:47 +03:00
EASY_FUNCTION(profiler::colors::Magenta); // Magenta block with name "frame"
2016-09-07 22:12:25 +03:00
prepareRender();
calculatePhysics();
2016-06-29 06:47:50 +04:00
}
```
2016-09-15 00:08:53 +03:00
To profile any block you may do this as following.
You can specify these blocks also with Google material design colors or just set name of the block
2016-09-15 00:33:47 +03:00
(in this case it will have default color which is `Amber100` ):
2016-06-29 06:47:50 +04:00
```cpp
2016-10-21 22:21:25 +03:00
#include <easy/profiler.h>
2016-08-31 22:47:17 +03:00
2016-11-06 03:56:30 +03:00
void foo() {
2016-09-15 00:08:53 +03:00
// some code
2016-09-15 00:33:47 +03:00
EASY_BLOCK("Calculating sum"); // Block with default color
2016-09-15 00:08:53 +03:00
int sum = 0;
2016-11-06 03:56:30 +03:00
for (int i = 0; i < 10 ; + + i ) {
EASY_BLOCK("Addition", profiler::colors::Red); // Scoped red block (no EASY_END_BLOCK needed)
2016-09-07 22:12:25 +03:00
sum += i;
2016-11-06 03:56:30 +03:00
}
EASY_END_BLOCK; // This ends "Calculating sum" block
2016-09-07 22:12:25 +03:00
2016-09-15 00:33:47 +03:00
EASY_BLOCK("Calculating multiplication", profiler::colors::Blue500); // Blue block
2016-09-15 00:08:53 +03:00
int mul = 1;
for (int i = 1; i < 11 ; + + i )
2016-09-07 22:12:25 +03:00
mul *= i;
2016-11-06 03:56:30 +03:00
//EASY_END_BLOCK; // This is not needed because all blocks are ended on destructor when closing braces met
2016-06-29 06:47:50 +04:00
}
```
2016-09-15 00:08:53 +03:00
2016-09-15 00:33:47 +03:00
You can also use your own colors. easy_profiler is using standard 32-bit ARGB color format.
2016-09-15 00:08:53 +03:00
Example:
```cpp
2016-10-21 22:21:25 +03:00
#include <easy/profiler.h>
2016-09-15 00:08:53 +03:00
2016-11-06 03:56:30 +03:00
void bar() {
2016-09-15 00:33:47 +03:00
EASY_FUNCTION(0xfff080aa); // Function block with custom color
2016-09-15 00:08:53 +03:00
// some code
}
```
2016-09-26 22:00:22 +03:00
# Build
## Prerequisites
For core:
* compiler with c++11 support
2016-11-13 15:54:06 +03:00
* cmake 3.0 or higher
2016-09-26 22:00:22 +03:00
For GUI:
2016-11-13 15:54:06 +03:00
* Qt 5.3.0 or higher
2016-09-26 22:00:22 +03:00
## Linux
```bash
$ mkdir build
$ cd build
$ cmake ..
$ make
```
## Windows
If you are using QtCreator IDE you can just open `CMakeLists.txt` file in root directory.
If you are using Visual Studio you can generate solution by cmake generator command.
2016-11-13 15:54:06 +03:00
Examples shows how to generate Win64 solution for Visual Studio 2013. To generate for another version use proper cmake generator (-G "name of generator").
2016-09-26 22:00:22 +03:00
### Way 1
Specify path to cmake scripts in Qt5 dir (usually in lib/cmake subdir) and execute cmake generator command,
for example:
```batch
$ mkdir build
$ cd build
$ cmake -DCMAKE_PREFIX_PATH="C:\Qt\5.3\msvc2013_64\lib\cmake" .. -G "Visual Studio 12 2013 Win64"
```
### Way 2
Create system variable "Qt5Widgets_DIR" and set it's value to "[path-to-Qt5-binaries]\lib\cmake\Qt5Widgets".
For example, "C:\Qt\5.3\msvc2013_64\lib\cmake\Qt5Widgets".
And then run cmake generator as follows:
```batch
$ mkdir build
$ cd build
$ cmake .. -G "Visual Studio 12 2013 Win64"
```
2016-08-31 22:47:17 +03:00
[![Analytics ](https://ga-beacon.appspot.com/UA-82899176-1/easy_profiler/readme )](https://github.com/yse/easy_profiler)