[SERVER-70892] Evaluate if we can use modern standalone tcmalloc Created: 27/Oct/22  Updated: 05/Dec/22  Resolved: 27/Oct/22

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

Type: Task Priority: Major - P3
Reporter: Tyler Brock Assignee: Backlog - Service Architecture
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Assigned Teams:
Service Arch
Participants:

 Description   

Our current version of tcmalloc which comes from gperftools. Over time the tcmalloc standalone library which google uses in production has diverged from the version that comes with gperftools.

See: https://google.github.io/tcmalloc/gperftools.html

Modern versions of tcmalloc (the standalone library) have a new mode of operation, "per-CPU caching", where the library maintains memory caches local to individual logical cores on Linux >= 4.18 where restartable sequences are supported and falls back to older per-thread behavior when not supported.

We should evaluate whether or not we could "upgrade" to the standalone tcmalloc to take advantage of per-core caches.


Generated at Thu Feb 08 06:17:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.