Closed Bug 1352235 Opened 8 years ago Closed 8 years ago

NodeInfoManager should use a local cache for recently used nodeinfos to avoid slow hashtable lookups

Categories

(Core :: DOM: Core & HTML, enhancement)

50 Branch
enhancement
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla55
Tracking Status
firefox55 --- fixed

People

(Reporter: smaug, Assigned: smaug)

References

Details

Attachments

(1 file, 1 obsolete file)

Attached patch wip (obsolete) — Splinter Review
This has also a fix relying on bug 1351303.
Attached patch v2Splinter Review
Without the bug 1351303 stuff.
Attachment #8853146 - Attachment is obsolete: true
Comment on attachment 8853148 [details] [diff] [review] v2 -m "Bug 1352235, try to avoid slow hashtable lookups when getting a nodeinfo, r=bz" 31 is rather magical prime number. We use currently that in ContentLists and I use the same in NS_Atomize fix. Can't easily avoid minor code duplication since there are those two ways to get NodeInfo, one using nsIAtom, one using nsAString.
Attachment #8853148 - Flags: review?(bzbarsky)
Attachment #8853148 - Flags: review?(bzbarsky) → review+
Pushed by opettay@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/71bcf82f64b9 try to avoid slow hashtable lookups when getting a nodeinfo, r=bz
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: