Speed up per-tab profiling of JS by skipping the expensive string hashing.

RESOLVED FIXED in mozilla27

Status

()

defect
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: njn, Assigned: njn)

Tracking

unspecified
mozilla27
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

The string hashing done in JS memory profiling is expensive and not used by the
per-tab measurements.
Time taken to profile JS memory:

                before  after
gmail.com       21ms    7ms
techcrunch.com  19ms    9ms

With the patch applied, |perf| tells me that there is nothing beyond that worth
optimizing -- most of the time is spent in malloc_usable_size().
Attachment #822151 - Flags: review?(till)
Comment on attachment 822151 [details] [diff] [review]
Speed up per-tab profiling of JS by skipping the expensive string hashing.

Review of attachment 822151 [details] [diff] [review]:
-----------------------------------------------------------------

nice!
Attachment #822151 - Flags: review?(till) → review+
https://hg.mozilla.org/mozilla-central/rev/2d537818dfb9
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla27
You need to log in before you can comment on or make changes to this bug.