Closed
Bug 558795
Opened 15 years ago
Closed 15 years ago
Investigate how to speed up nsEventTargetChainItem (de)allocation
Categories
(Core :: DOM: Events, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: smaug, Assigned: smaug)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
(deleted),
patch
|
jst
:
review+
|
Details | Diff | Splinter Review |
Currently nsFixedSizeAllocator is used, but it shows up surprisingly
high in the Shark profiles.
Perhaps nsEventTargetChainItem could be cached in a linked list or something like
that and release them only if large amount of objects has been released.
|
Assignee | |
Comment 1•15 years ago
|
||
This should do it. We allocate ETCI objects from pool (so that locality should
be reasonable good) and release the whole pool when needed.
But usually we can just cache ETCI objects.
The patch gives ~4% speed up in event *dispatch*.
I posted the patch to tryserver.
Attachment #438714 -
Flags: review?(jst)
|
||
Updated•15 years ago
|
Attachment #438714 -
Flags: review?(jst) → review+
|
|
Assignee | |
Comment 2•15 years ago
|
||
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•