3 ms·
Oddly enough I've written about those results before: https://www.dropbox.com/scl/fi/evnn6yoornh9p6l7nq1t9/Irreproducible-malloc-benchmarks.paper?rlkey=73mi4op
by jeffbee 2y ago
Oddly enough I've written about those results before:
https://www.dropbox.com/scl/fi/evnn6yoornh9p6l7nq1t9/Irreproducible-malloc-benchmarks.paper?rlkey=73mi4op4hfn7euqmry9bmnxtr&dl=0 https://www.dropbox.com/scl/fi/evnn6yoornh9p6l7nq1t9/Irrepro...
- vlovich123 2y agobut we all can agree that glibc is trash right? :) I’d be careful extrapolating from just one benchmark but generally if I had to choose I’d pick the new tcmalloc if I could. It seems to be a higher quality codebase.
- jeffbee 2y agoThe problem with the current tcmalloc, which I agree is very good, is the difficulty of integrating it with random builds. It works well for large systems and especially those that are already bazelized, but I couldn't whip up a quick way to link it to `jq` in this gist.