Last Comment Bug 694335 - Enable jemalloc on MacOS 10.5
: Enable jemalloc on MacOS 10.5
Product: Core
Classification: Components
Component: Memory Allocator (show other bugs)
: unspecified
: x86 Mac OS X
: -- normal (vote)
: mozilla10
Assigned To: Justin Lebar (not reading bugmail)
: Mike Hommey [:glandium]
Depends on: 670492 693404 699101 702250
  Show dependency treegraph
Reported: 2011-10-13 08:53 PDT by Justin Lebar (not reading bugmail)
Modified: 2012-01-05 13:26 PST (History)
10 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---

Patch v1 (1.86 KB, patch)
2011-10-27 08:29 PDT, Justin Lebar (not reading bugmail)
khuey: review+
Details | Diff | Splinter Review

Description Justin Lebar (not reading bugmail) 2011-10-13 08:53:30 PDT
(This was originally bug 693404, but that one has morphed into a different issue.)

jemalloc is currently disabled on Mac due to a TP5-RSS regression, bug 670492.

I think this regression is bogus.  We can use the work in bug 693404 to determine whether the regression is real or not.

Once we've definitively established whether jemalloc on 10.5 is a memory win, I think we should consider enabling jemalloc on 10.5, even before we get Talos set up to measure memory usage on 10.5 properly, because jmaher says it may take months to change Talos (bug 693404 comment 17).
Comment 1 Jesse Ruderman 2011-10-18 21:54:20 PDT
I'm not sure this is worth working on, given that Apple has stopped issuing security updates for Mac OS X 10.5.
Comment 2 Justin Lebar (not reading bugmail) 2011-10-19 05:37:16 PDT
Can we get some data about how many users are on 10.5?

I think so long as we won't check something in if it regresses 10.5, we should consider taking this.  It's not a hard thing; in theory, anyway, we just need to flip a switch.
Comment 3 Justin Lebar (not reading bugmail) 2011-10-27 08:29:00 PDT
Created attachment 569983 [details] [diff] [review]
Patch v1
Comment 4 Justin Lebar (not reading bugmail) 2011-10-27 08:30:03 PDT
I just tested on the 10.5 machine we have in the office.

Test case: Open techcrunch, cnn.  Close both tabs.  Open about:memory, click minimize memory usage.

Latest trunk: 120mb.
With jemalloc enabled: 105mb.
Comment 5 Justin Lebar (not reading bugmail) 2011-10-27 08:30:51 PDT
We'll need to write to dev.tree-management before we push this, since it's going to look like a big regression.
Comment 6 Kyle Huey [:khuey] (Exited; not receiving bugmail, email if necessary) 2011-10-31 06:04:33 PDT
Comment on attachment 569983 [details] [diff] [review]
Patch v1

Review of attachment 569983 [details] [diff] [review]:

Well that was easy.
Comment 7 Justin Lebar (not reading bugmail) 2011-10-31 11:52:45 PDT
Comment 8 Justin Lebar (not reading bugmail) 2011-10-31 18:58:32 PDT
Awesome, this was an 8% TP5 win.!topic/
Comment 9 Nicholas Nethercote [:njn] 2011-10-31 19:19:52 PDT
I see this:

  Talos Regression :( Tp5 MozAfterPaint (RSS) increase 18.4% on MacOSX 10.5.8 Mozilla-Inbound

Followed by this:

  Talos Improvement! Tp5 MozAfterPaint decrease 7.93% on MacOSX 10.5.8 Mozilla-Inbound
Comment 10 Justin Lebar (not reading bugmail) 2011-10-31 19:24:55 PDT
Right.  The RSS regression is expected and bogus.  The TP5 speed improvement is neither.  :)
Comment 11 Kyle Huey [:khuey] (Exited; not receiving bugmail, email if necessary) 2011-11-01 07:35:46 PDT
Comment 12 Justin Lebar (not reading bugmail) 2011-11-02 22:28:06 PDT
This is a big change that we should track for FF10.
Comment 13 Justin Lebar (not reading bugmail) 2011-11-16 14:00:23 PST
Unfortunately we're going to have to back this out of FF10, due to what appears to be an OS-level bug.  Bummer.

Discussion has been in bug 702250.

Note You need to log in before you can comment on or make changes to this bug.