#profiling

rust_hawktracer

Rust bindings for hawktracer profiling library

8 releases (5 breaking)

✓ Uses Rust 2018 edition

0.6.0 Nov 30, 2019
0.5.0 Nov 17, 2019
0.4.0 Jan 19, 2019
0.3.2 Jan 19, 2019
0.1.1 Sep 16, 2018

#8 in Profiling

Download history 126/week @ 2019-08-24 85/week @ 2019-08-31 8/week @ 2019-09-07 67/week @ 2019-09-14 51/week @ 2019-09-21 9/week @ 2019-09-28 10/week @ 2019-10-05 33/week @ 2019-10-12 18/week @ 2019-10-19 54/week @ 2019-10-26 15/week @ 2019-11-02 6/week @ 2019-11-09 153/week @ 2019-11-16 153/week @ 2019-11-23

221 downloads per month

MIT/Apache

6KB

Crates.io

rust_hawktracer

Rust bindings for the Hawktracer profiler.
This crate offers simple, minimal bindings to help you profile your rust programs.
If profiling is not enabled by specifying features=["profiling_enabled"], having tracepoints in your code has absolutely no overhead (everything gets removed at compile time).

alt text

Tools needed

You need an external tool in order to transform captured profiling data from a binary format to something that can be interpreted by chrome:://tracing (or other clients).

Profiling code

In Cargo.toml:

[dependencies.rust_hawktracer]
version = "0.6"
features=["profiling_enabled"]

If the bindings that come with it don't match what your platform expects change it to:

features=["profiling_enabled", "generate_bindings"]

In your main.rs:

#[macro_use]
extern crate rust_hawktracer;
use rust_hawktracer::*;
use std::{thread, time};

#[hawktracer(trace_this)]
fn method_to_trace() {
    thread::sleep(time::Duration::from_millis(1));
}

fn main() {
    let instance = HawktracerInstance::new();
    let _listener = instance.create_listener(HawktracerListenerType::ToFile {
        file_path: "trace.bin".into(),
        buffer_size: 4096,
    });

    // For a networked listner
    // let _listener = instance.create_listener(HawktracerListenerType::TCP {
    //     port: 12345,
    //     buffer_size: 4096,
    // });

    println!("Hello, world!");
    {
        scoped_tracepoint!(_test);
        thread::sleep(time::Duration::from_millis(10));

        {
            for _ in 0..10 {
                scoped_tracepoint!(_second_tracepoint);
                thread::sleep(time::Duration::from_millis(10));
            }
        }
    }
}

Visualization

I recommend getting hawktracer_converter using cargo install hawktracer-converter as described here.

If you use HawktracerListenerType::ToFile:

.\hawktracer-converter.exe --source trace.bin --output trace.json

If you use HawktracerListenerType::TCP you can listen and capture traces by specifying the IP:port as the --source parameter:

.\hawktracer-converter.exe --source 127.0.0.1:12345 --output trace.json

Open a chrome browser and go to this address: chrome://tracing/

By opening the trace.json for the program above you should see something like:

alt text

Things to watch out for

In rust macros I can't create new identifier names. This means that if you want to avoid warnings, the tracepoint names have to start with a leading _, as in scoped_tracepoint!(_my_tracepoint_name).
This doesn't apply to the function annotations.

License

Licensed under either of

at your option.

Dependencies

~3–305KB