Spotting and Avoiding Heap Fragmentation in Rust Applications

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • rfcs

    RFCs for changes to Rust

  • I'm not sure it's the case that there's something "wrong" with the default allocator, but rather that there are different tradeoffs at play. There's an old but good discussion of the issue here https://github.com/rust-lang/rfcs/blob/master/text/1183-swap...

  • tcmalloc

  • > * Switching from libc malloc to tcmalloc (dating myself a little bit)

    If you think of tcmalloc as an old crusty allocator, you've probably only seen the gperftools version of it.

    This is the version Google now uses internally: https://github.com/google/tcmalloc

    It's worth a fresh look. In particular, it supports per-CPU caches as an alternative to per-thread caches. Those are fantastic if you have a lot more threads than CPUs.

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
  • hubris

    A lightweight, memory-protected, message-passing kernel for deeply embedded systems.

  • everywhere, for example in https://github.com/oxidecomputer/hubris/search?q=dyn

    Is Box really allocating here? Is the "Rust By Example" text incomplete?

    Then I had to stop learning Rust for other reasons, but this doubt really hit me at the time.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts