[SERVER-31839] Investigate JEMalloc Performance Versus TCMalloc Created: 06/Nov/17  Updated: 01/Feb/19  Resolved: 29/Jan/18

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Gregory McKeon (Inactive) Assignee: Mark Benvenuto
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-16773 Performance degradation due to TCMall... Closed
related to SERVER-39325 Add support for "allocator=jemalloc" Backlog
related to SERVER-24268 Investigate jemalloc as alternative t... Closed
Backwards Compatibility: Fully Compatible
Sprint: Platforms 2018-01-01, Platforms 2018-01-15, Platforms 2018-01-29
Participants:

 Description   

Determine whether we we want to stick with using TCMalloc or switch to JEMalloc.



 Comments   
Comment by Bruce Lucas (Inactive) [ 12/Dec/17 ]

In addition to performance, we would need to investigate whether jemalloc provides (our could be made to provide) the necessary hooks to support the built-in heap profiler, as this has enabled us to track down a number of memory usage bugs in the field.

Generated at Thu Feb 08 04:28:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.