yeah that’s a common mistake when evaluating tcmalloc. gperftools tcmalloc diverged quite a while ago. doesn’t have a lot of the fancier features of modern tcmalloc [0].

[0]: https://github.com/google/tcmalloc/blob/master/docs/gperftoo...