Closed
Bug 1517062
Opened 6 years ago
Closed 6 years ago
ContentBlockingLog::RecordLog() is slow due to hashtable lookup
Categories
(Core :: DOM: Core & HTML, defect, P2)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla66
| Tracking | Status | |
|---|---|---|
| firefox66 | --- | fixed |
People
(Reporter: ehsan.akhgari, Assigned: ehsan.akhgari)
References
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
See https://perfht.ml/2QZ2jH0. I knew I was going to regret using a hashtable. :-(
|
Assignee | |
Comment 1•6 years ago
|
||
Pushed by eakhgari@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/336f511efe6b
Stop using a hashtable in ContentBlockingLog; r=baku
|
||
Updated•6 years ago
|
Priority: -- → P2
|
||
Comment 3•6 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox66:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
|
||
Updated•6 years ago
|
Assignee: nobody → ehsan
|
||
Comment 4•6 years ago
|
||
https://hg.mozilla.org/projects/cedar/rev/336f511efe6b53efea61c7e7d936510de801b6d4
Bug 1517062 - Stop using a hashtable in ContentBlockingLog; r=baku
|
||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•