- 61comments
- 137comments
- 35comments
- 84comments
- 56comments
- 7comments
- 313comments
- 44comments
- —discuss
- 26comments
- 55comments
- 154comments
- 624comments
- —discuss
- 248comments
- 96comments
- 173comments
- 78comments
- 10comments
- 239comments
- 51comments
- 142comments
- —discuss
- 165comments
- 20comments
- 28comments
- 30comments
- 72comments
- 48comments
- —discuss
Currently, it's unclear why - I didn't find any information in their public channels.
They un-archived it today long enough to revert a change to the purging algorithm that was merged in March [0]. The first archive date I saw this morning was from the last week of May. I won't speculate about the reason, but it's a small relief that the archiving seems deliberate and that the maintainers are still active.
[0] https://github.com/jemalloc/jemalloc/commit/27d7960cf9b48a9a...
More: https://github.com/facebook/jemalloc/discussions/7
We once went through the effort to use jemalloc for workloads which were highly optimized particularly for NUMA.
Incredibly, it had absolutely zero performance improvement. I’ve always wondered how that was possible. Spent a fair bit of time confirming the memory layout and NUMA node ownership etc. It was working, it just.. did nothing!
Why? The prior conversation (linked here in this posting thread) has somebody asking the same question. And a comment: did nothing. So it could be the variant has low enough achievement over other *alloc that it was felt best to retire it.
Performance of jemalloc is good, hope to know why it is archived
Looks like it got forked to https://github.com/facebook/jemalloc