Summary: | Add a balanced benchmark for QuerySelector | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Benjamin Poulain <benjamin> | ||||
Component: | New Bugs | Assignee: | Benjamin Poulain <benjamin> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | rniwa | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
Benjamin Poulain
2013-05-27 01:52:07 PDT
Created attachment 202955 [details]
Patch
I get 0.59% when run with run-pert-tests. 1.2% when run in Safari. By the way, there are other weird tests for query selectors. And they are in Parser/ for some reason. Comment on attachment 202955 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=202955&action=review > PerformanceTests/ChangeLog:18 > + * DOM/QuerySelector.html: Added. > + * DOM/resources/query-selector.html: Added. We shouldn't be adding new tests to DOM for now since they're tests imported from chromium's dom_perf test. They are two tests misplaced there but... > > PerformanceTests/ChangeLog:18
> > + * DOM/QuerySelector.html: Added.
> > + * DOM/resources/query-selector.html: Added.
>
> We shouldn't be adding new tests to DOM for now since they're tests imported from chromium's dom_perf test.
> They are two tests misplaced there but...
Okay, that explain why the others are in Parser/.
Any suggestion where to put this test?
(In reply to comment #4) > > Okay, that explain why the others are in Parser/. > Any suggestion where to put this test? CSS? Committed r150781: <http://trac.webkit.org/changeset/150781> |