Closed
Bug 1499726
Opened 7 years ago
Closed 7 years ago
make main-thread XHR timer setting slightly more efficient
Categories
(Core :: DOM: Core & HTML, enhancement, P2)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla64
| Tracking | Status | |
|---|---|---|
| firefox64 | --- | fixed |
People
(Reporter: froydnj, Assigned: froydnj)
Details
Attachments
(1 file)
|
4.23 KB,
patch
|
baku
:
review+
|
Details | Diff | Splinter Review |
Instead of creating a timer and then setting the timer's target, we can
determine the timer's target and pass it in directly when the timer is
created. This reordering of steps is slightly more efficient, since
SetTarget() is both a virtual call and requires locking, both of which
can be skipped if we know the target at timer creation time.
|
Assignee | |
Comment 1•7 years ago
|
||
Attachment #9017863 -
Flags: review?(amarchesini)
|
||
Updated•7 years ago
|
Attachment #9017863 -
Flags: review?(amarchesini) → review+
|
||
Updated•7 years ago
|
Priority: -- → P2
Pushed by nfroyd@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/706f1a7eae88
make main-thread XHR timer setting slightly more efficient; r=baku
|
|
||
Comment 3•7 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox64:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
|
||
Updated•7 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•