10 releases

0.3.0 Mar 20, 2019
0.1.9 Jul 4, 2018
0.1.8 May 22, 2018
0.1.7 Apr 27, 2018
0.1.0 Jan 21, 2016

#3 in Memory management

Download history 334/week @ 2018-12-20 442/week @ 2018-12-27 486/week @ 2019-01-03 417/week @ 2019-01-10 591/week @ 2019-01-17 823/week @ 2019-01-24 1308/week @ 2019-01-31 1082/week @ 2019-02-07 1542/week @ 2019-02-14 1972/week @ 2019-02-21 2442/week @ 2019-02-28 2030/week @ 2019-03-07 2546/week @ 2019-03-14 3963/week @ 2019-03-21 3969/week @ 2019-03-28

7,783 downloads per month
Used in 14 crates

MIT/Apache

1MB
31K SLoC

C 29K SLoC // 0.1% comments Rust 756 SLoC // 0.5% comments Shell 590 SLoC // 0.2% comments C++ 213 SLoC // 0.1% comments Python 161 SLoC // 0.1% comments XSL 9 SLoC

jemallocator

Travis-CI Status Appveyor Status Latest Version docs

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

Overview

The jemalloc support ecosystem consists of the following crates:

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

Documentation

To use jemallocator add it as a dependency:

# Cargo.toml
[dependencies]
jemallocator = "0.1.8"

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

extern crate jemallocator;

#[global_allocator]
static ALLOC: jemallocator::Jemalloc = jemallocator::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 jemallocator and jemalloc-sys tests pass on the target?
  • jemalloc: do 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
aarch64-unknown-linux-gnu
arm-unknown-linux-gnueabi
armv7-unknown-linux-gnueabi
i586-unknown-linux-gnu
i686-unknown-linux-gnu (tier 1)
mips-unknown-linux-gnu
mipsel-unknown-linux-musl
mips64-unknown-linux-gnuabi64
mips64el-unknown-linux-gnuabi64
powerpc-unknown-linux-gnu
powerpc64-unknown-linux-gnu
powerpc64le-unknown-linux-gnu
x86_64-unknown-linux-gnu (tier 1)
MacOSX targets: build run jemalloc valgrind
x86_64-apple-darwin (tier 1)
i686-apple-darwin (tier 1)
Windows targets: build run jemalloc valgrind
x86_64-pc-windows-msvc (tier 1)
i686-pc-windows-msvc (tier 1)
x86_64-pc-windows-gnu (tier 1)
i686-pc-windows-gnu (tier 1)
Android targets: build run jemalloc valgrind
aarch64-linux-android
x86_64-linux-android

Features

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

License

This project is licensed under either of

at your option.

Contribution

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

Dependencies