fix: use new memory allocator 'jemallocator' in aggregator

This will likely avoid having memory fragmentation resulting in RES memory not being correctly released.

Author: jpraynaud

Cargo.lock

@@ -46,6 +46,9 @@ uuid = { version = "1.7.0", features = ["v4", "fast-rng", "macro-diagnostics"] }
 warp = "0.3.6"
 zstd = { version = "0.13.0", features = ["zstdmt"] }
 
+[target.'cfg(not(target_env = "msvc"))'.dependencies]
+tikv-jemallocator = { version = "0.5.4", optional = true }
+
 [dev-dependencies]
 httpmock = "0.7.0"
 mithril-common = { path = "../mithril-common", features = [
@@ -57,4 +60,7 @@ slog-term = "2.9.0"
 tempfile = "3.9.0"
 
 [features]
+default = ["jemallocator"]
+
 bundle_openssl = ["dep:openssl", "dep:openssl-probe"]
+jemallocator = ["dep:tikv-jemallocator"]

mithril-aggregator/Cargo.toml

@@ -64,6 +64,14 @@ pub use tools::{
 #[cfg(test)]
 pub use dependency_injection::tests::initialize_dependencies;
 
+// Memory allocator (to handle properly memory fragmentation)
+#[cfg(all(not(target_env = "msvc"), feature = "jemallocator"))]
+use tikv_jemallocator::Jemalloc;
+
+#[cfg(all(not(target_env = "msvc"), feature = "jemallocator"))]
+#[global_allocator]
+static GLOBAL: Jemalloc = Jemalloc;
+
 #[cfg(test)]
 pub(crate) mod test_tools {
     use slog::Drain;