#alloc #stats #instrument #statistics

dev stats_alloc

An allocator wrapper that allows for instrumenting global allocators

11 releases

Uses old Rust 2015

0.1.10 Mar 30, 2022
0.1.9 Mar 30, 2022
0.1.8 May 13, 2019
0.1.6 Aug 3, 2018

#26 in Memory management

Download history 37251/week @ 2023-12-18 9817/week @ 2023-12-25 30241/week @ 2024-01-01 40259/week @ 2024-01-08 44879/week @ 2024-01-15 43759/week @ 2024-01-22 36466/week @ 2024-01-29 44392/week @ 2024-02-05 41525/week @ 2024-02-12 43844/week @ 2024-02-19 53425/week @ 2024-02-26 53652/week @ 2024-03-04 35581/week @ 2024-03-11 39512/week @ 2024-03-18 44132/week @ 2024-03-25 56278/week @ 2024-04-01

176,769 downloads per month
Used in 16 crates

MIT license

13KB
188 lines

stats_alloc

An instrumenting middleware for global allocators in Rust, useful in testing for validating assumptions regarding allocation patterns, and potentially in production loads to monitor for memory leaks.

Example

extern crate stats_alloc;

use stats_alloc::{StatsAlloc, Region, INSTRUMENTED_SYSTEM};
use std::alloc::System;

#[global_allocator]
static GLOBAL: &StatsAlloc<System> = &INSTRUMENTED_SYSTEM;

fn example_using_region() {
    let reg = Region::new(&GLOBAL);
    let x: Vec<u8> = Vec::with_capacity(1_024);
    println!("Stats at 1: {:#?}", reg.change());
    // Used here to ensure that the value is not
    // dropped before we check the statistics
    ::std::mem::size_of_val(&x);
}

Custom allocators

Currenty wrapping a custom allocator requires the use of the nightly compiler and compiling with the "nightly" feature due to the soon to stabilize use of the unstable const_fn_trait_bound and the fact that the internals of the instrumenting type are not public. If that's fine with you, a custom allocator can be wrapped as follows:

#[global_allocator]
static GLOBAL: StatsAlloc<System> = StatsAlloc::new(MyCustomAllocator::new());

No runtime deps

Features