4 ms·
This problem hit the Ruby community hard about 5 years ago. Basically everyone uses jemalloc or tcmalloc in production in the Ruby community nowadays. What fru
by nateberkopec 6y ago
This problem hit the Ruby community hard about 5 years ago.
Basically everyone uses jemalloc or tcmalloc in production in the Ruby community nowadays. What frustrates me is the malloc community's sort of blase reaction along the lines of "there's no bug, this is expected behavior".
- volgar1x 6y agoWhy try to optimize for every cases possible ? Use the right tool for the right job.
- nateberkopec 6y ago"multihreaded programs" seems like a pretty big use case, and it seems to occur in just about every major multithreaded C program using glibc malloc. I would agree with you if it didn't seem like other allocators are solving this without any tradeoffs.