FS#51077 - [firefox] Use jemalloc
Attached to Project:
Arch Linux
Opened by Constantine (Hi-Angel) - Friday, 30 September 2016, 12:03 GMT
Last edited by Jan de Groot (JGC) - Monday, 03 October 2016, 15:03 GMT
Opened by Constantine (Hi-Angel) - Friday, 30 September 2016, 12:03 GMT
Last edited by Jan de Groot (JGC) - Monday, 03 October 2016, 15:03 GMT
|
Details
Looking the "about:buildconfig", there's no
"--enable-jemalloc" configure option, which Windows users
report to have.
"jemalloc" is an implementation of memory allocation that reported to have a better performance (at least for firefox case). |
This task depends upon
I don't think it's wise to divert from upstream decisions on memory allocators here.
Well, I actually came here from the comments of the article about Mesa switch to jemalloc¹, and for them it indeed gave a performance increase. I suppose, i.e. libc didn't switch to that algorithm because it may be benefits to specific workloads, but as Windows version did the switch long ago, Mozilla developers have probably found Firefox to be that kind of workload.
[1]: https://www.phoronix.com/scan.php?page=news_item&px=Mesa-RFC-Jemalloc
I don't care about the performance stuff, it's about stability. All upstream tests on linux are done with the default settings, deviating from those will make our builds extremely untested and problems will be hard to debug.