Bug 79231 - Add performance tests for the getters/setters of Element attributes
Summary: Add performance tests for the getters/setters of Element attributes
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Kentaro Hara
Depends on:
Blocks: 79208
  Show dependency treegraph
Reported: 2012-02-22 05:49 PST by Kentaro Hara
Modified: 2012-02-23 01:19 PST (History)
2 users (show)

See Also:

Patch (22.18 KB, patch)
2012-02-22 06:12 PST, Kentaro Hara
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Kentaro Hara 2012-02-22 05:49:09 PST
We can add micro-benchmark performance tests for the getters/setters of Element attributes.
Comment 1 Kentaro Hara 2012-02-22 06:04:03 PST
We can omit the performance tests for onabort, onblur, onchange, onclick, oncontextmenu, ondblclick, ondrag, ondragend, ondragenter, ondragleave, ondragover, ondragstart, ondrop, onerror, onfocus, oninput, oninvalid, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, onmousewheel, onscroll, onselect, onsubmit, onbeforecut, oncut, onbeforecopy, oncopy, onbeforepaste, onpaste, onreset, onsearch, onselectstart, onwebkitfullscreenchange, and onwebkitfullscreenerror, because they trace almost the same call-path as onload.
Comment 2 Kentaro Hara 2012-02-22 06:12:18 PST
Created attachment 128195 [details]
Comment 3 Ryosuke Niwa 2012-02-22 06:36:58 PST
Comment on attachment 128195 [details]

We can not add this many tests for each getter/setter? It's gonna increase performance bot's cycle time a lot.