17 releases

Uses old Rust 2015

0.2.2 Mar 8, 2018
0.2.1-pre2 Apr 19, 2018
0.2.0 Jul 10, 2017
0.1.11 Jan 2, 2017
0.1.2 Nov 25, 2015
Download history 316/week @ 2021-08-10 227/week @ 2021-08-17 572/week @ 2021-08-24 304/week @ 2021-08-31 488/week @ 2021-09-07 401/week @ 2021-09-14 288/week @ 2021-09-21 335/week @ 2021-09-28 261/week @ 2021-10-05 309/week @ 2021-10-12 257/week @ 2021-10-19 332/week @ 2021-10-26 469/week @ 2021-11-02 321/week @ 2021-11-09 371/week @ 2021-11-16 300/week @ 2021-11-23

1,533 downloads per month
Used in less than 18 crates


13K SLoC

JavaScript 10K SLoC // 0.0% comments TypeScript 2K SLoC // 0.3% comments Rust 459 SLoC // 0.0% comments


A cool flamegraph library for rust

Flamegraphs are a great way to view profiling information. At a glance, they give you information about how much time your program spends in critical sections of your code giving you some much-needed insight into where optimizations may be needed.

Unlike tools like perf which have the OS interrupt your running program repeatadly and reports on every function in your callstack, FLAME lets you choose what you want to see in the graph by adding performance instrumentation to your own code.

Simply use any of FLAMEs APIs to annotate the start and end of a block code that you want timing information from, and FLAME will organize these timings hierarchically.


Here's an example of how to use some of FLAMEs APIs:

extern crate flame;

use std::fs::File;

fn main() {
    // Manual `start` and `end`
    flame::start("read file");
    let x = read_a_file();
    flame::end("read file");

    // Time the execution of a closure.  (the result of the closure is returned)
    let y = flame::span_of("database query", || query_database());

    // Time the execution of a block by creating a guard.
    let z = {
        let _guard = flame::start_guard("cpu-heavy calculation");
        // Notes can be used to annotate a particular instant in time.
        flame::note("something interesting happened", None);

    // Dump the report to disk
    flame::dump_html(&mut File::create("flame-graph.html").unwrap()).unwrap();
    // Or read and process the data yourself!
    let spans = flame::spans();
    println!("{} {} {}", x, y, z);

And here's a screenshot of a flamegraph produced by dump_html (from a different project):


llogiq has created flamer, a compiler plugin that automatically inserts FLAME instrumentation into annotated functions allowing you to write code like

fn this_function_is_profiled() {

So if you are using a nightly version of rust, check it out; flamer is probably the easiest way to use FLAME!