Hacker ApprovedDepartments

tcmalloc

Ranked 4 of 4 memory allocators by recommenders

Google's memory allocator that people find fast and space efficient. Critics say it performs about the same as jemalloc, and note poor huge-page behavior.

Google's memory allocator that people find fast and space efficient. Critics say it performs about the same as jemalloc, and note poor huge-page behavior.

11 people gave an opinion

recommend it
7
criticize it
4
approval share
64%
Each figure is one person. RecommendsCriticizes

Recommended in 4 of 13 months

  1. November 2025: not recommended
  2. December 2025: not recommended
  3. January 2026: not recommended
  4. February 2026: not recommended
  5. March 2026: recommended
  6. April 2026: not recommended
  7. May 2026: not recommended
  8. June 2026: recommended
  9. July 2026: not recommended
  10. August 2026: recommended
  11. September 2026: recommended
  12. October 2026: not recommended
  13. November 2026: not recommended (month in progress)

Why it doesn’t carry the badge

  • 7 people recommend itNeeds 10 or more, not met.
  • 1.7 recommenders for every criticNeeds 2 to 1 or better, not met.
  • Recommended in 4 of 13 monthsNeeds 4 or more, met.

The same three rules apply to every product, and the badge can’t be bought. How the badge works

What people say about it

The reasons people give, with the number of comments that give each one. Open a reason to read what they said.

Why people recommend it

Each mark is one comment

  • Fast runtime performance

    “tc was among the fastest in runtime while being very space efficient”

    Comment from 17 Sep 2026 in “Comparison of Malloc() Algorithms”

    “When it comes to performance, the Google's tcmalloc is unconquered.”

    Comment from 16 Mar 2026 in “Jemalloc un-abandoned by Meta”

    “found (modern) tcmalloc to consistently win in time and space”

    Comment from 16 Mar 2026 in “Jemalloc un-abandoned by Meta”
  • Space efficient memory use

    “tc was among the fastest in runtime while being very space efficient”

    Comment from 17 Sep 2026 in “Comparison of Malloc() Algorithms”

    “found (modern) tcmalloc to consistently win in time and space”

    Comment from 16 Mar 2026 in “Jemalloc un-abandoned by Meta”
  • Comparable to jemalloc

    “Tcmalloc and jemalloc were neck to neck when comparing app metrics”

    Comment from 17 Mar 2026 in “Jemalloc un-abandoned by Meta”

    “they never seem to differ by more than a few percent”

    Comment from 16 Mar 2026 in “Jemalloc un-abandoned by Meta”

What people warn about

Each mark is one comment

  • Little gain over jemalloc

    “Tcmalloc and jemalloc were neck to neck when comparing app metrics”

    Comment from 17 Mar 2026 in “Jemalloc un-abandoned by Meta”

    “they never seem to differ by more than a few percent”

    Comment from 16 Mar 2026 in “Jemalloc un-abandoned by Meta”
  • Not enough for huge runtimes

    “A TCMalloc runtime is almost the same size as Java's most sophisticated GC, and it still can't keep up”

    Comment from 1 Sep 2026 in “Zig: Pointer Stability for ArrayLists”

    “huge runtimes like TCMalloc help, but not enough”

    Comment from 19 Sep 2026 in “What Zig felt like, coming from Rust”

Other memory allocators people recommend

The three most recommended other memory allocators, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.

tcmalloc compared with 3 alternatives
ProductRecommendCriticizeApprovalMonthsOwnedBadge
jemalloc341176%68 yrs3 ownersApproved
mimalloc22776%9—Approved
Bumpalo Rust crate8280%5——
tcmallocThis page7464%4——
See all 4 memory allocators, ranked

What people said

13 of the 15 comments that mention it, newest first. Each links to the original comment.

“huge runtimes like TCMalloc help, but not enough”

MixedComment from 19 Sep 2026 in “What Zig felt like, coming from Rust”

“our tests with a proprietary app led us to tcmalloc (new)”

RecommendsComment from 17 Sep 2026 in “Comparison of Malloc() Algorithms”

“tc was among the fastest in runtime while being very space efficient”

RecommendsComment from 17 Sep 2026 in “Comparison of Malloc() Algorithms”

“A TCMalloc runtime is almost the same size as Java's most sophisticated GC, and it still can't keep up”

CriticizesComment from 1 Sep 2026 in “Zig: Pointer Stability for ArrayLists”

“Having a not-dogshit allocator really doesn't hurt.”

RecommendsComment from 28 Aug 2026 in “Don't use musl if you care about performance”

“the common solution is to use tcmalloc or jemalloc which hasnt these problems?”

RecommendsComment from 6 Jun 2026 in “Lambda isn't leaking memory, your metrics are lying to you”

“6.19 breaking tcmalloc and Mongo”

CriticizesComment from 29 Apr 2026 in “Linux 7.0 Broke PostgreSQL: The Preemption Regression Explained”

“Tcmalloc and jemalloc were neck to neck when comparing app metrics”

MixedComment from 17 Mar 2026 in “Jemalloc un-abandoned by Meta”

“tcmalloc is actually the only allocator I tested which was not using thread local caches”

CriticizesComment from 17 Mar 2026 in “Jemalloc un-abandoned by Meta”

“When it comes to performance, the Google's tcmalloc is unconquered.”

RecommendsComment from 16 Mar 2026 in “Jemalloc un-abandoned by Meta”

“they never seem to differ by more than a few percent”

MixedComment from 16 Mar 2026 in “Jemalloc un-abandoned by Meta”

“found (modern) tcmalloc to consistently win in time and space”

RecommendsComment from 16 Mar 2026 in “Jemalloc un-abandoned by Meta”

“probably the single worst way to experience huge pages”

CriticizesComment from 1 Jan 2026 in “Memory Subsystem Optimizations”

Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.