#allocator #jemalloc


A Rust allocator backed by jemalloc

2 releases

0.4.1 Nov 17, 2020
0.4.0 Jul 21, 2020

#31 in Memory management

Download history 172/week @ 2020-12-24 189/week @ 2020-12-31 186/week @ 2021-01-07 132/week @ 2021-01-14 167/week @ 2021-01-21 140/week @ 2021-01-28 136/week @ 2021-02-04 100/week @ 2021-02-11 154/week @ 2021-02-18 173/week @ 2021-02-25 152/week @ 2021-03-04 171/week @ 2021-03-11 216/week @ 2021-03-18 206/week @ 2021-03-25 796/week @ 2021-04-01 2137/week @ 2021-04-08

692 downloads per month
Used in 2 crates


36K SLoC

C 33K SLoC // 0.1% comments Rust 743 SLoC // 0.1% comments Visual Studio Project 699 SLoC Shell 320 SLoC // 0.2% comments C++ 213 SLoC // 0.1% comments Python 141 SLoC // 0.4% comments Visual Studio Solution 125 SLoC XSL 9 SLoC


Travis-CI Status Latest Version docs

This project is a simplified fork of jemallocator focus on server.

Links against jemalloc and provides a Jemalloc unit type that implements the allocator APIs and can be set as the #[global_allocator]


The jemalloc support ecosystem consists of the following crates:

  • tikv-jemalloc-sys: builds and links against jemalloc exposing raw C bindings to it.
  • tikv-jemallocator: provides the Jemalloc type which implements the GlobalAlloc and Alloc traits.
  • tikv-jemalloc-ctl: high-level wrapper over jemalloc's control and introspection APIs (the mallctl*() family of functions and the MALLCTL NAMESPACE)'


To use tikv-jemallocator add it as a dependency:

# Cargo.toml

[target.'cfg(not(target_env = "msvc"))'.dependencies]
tikv-jemallocator = "0.4.0"

To set tikv_jemallocator::Jemalloc as the global allocator add this to your project:

# main.rs
#[cfg(not(target_env = "msvc"))]
use tikv_jemallocator::Jemalloc;

#[cfg(not(target_env = "msvc"))]
static GLOBAL: Jemalloc = Jemalloc;

And that's it! Once you've defined this static then jemalloc will be used for all allocations requested by Rust code in the same program.

Platform support

The following table describes the supported platforms:

  • build: does the library compile for the target?
  • run: do tikv-jemallocator and tikv-jemalloc-sys tests pass on the target?
  • jemalloc: do tikv-jemalloc's tests pass on the target?
  • valgrind: do the tests pass under valgrind?

Tier 1 targets are tested on all Rust channels (stable, beta, and nightly). All other targets are only tested on Rust nightly.

Linux targets: build run jemalloc valgrind
x86_64-unknown-linux-gnu (tier 1)
MacOSX targets: build run jemalloc valgrind
x86_64-apple-darwin (tier 1)


The tikv-jemallocator crate re-exports the features of the tikv-jemalloc-sys dependency.


This project is licensed under either of

at your option.


Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in tikv-jemallocator by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.