-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add new benchmark for css selectors #3647
Conversation
Create `selectors` directory and add `sizzle` submodule
The reasons for using try-catch are: * The list contains invalid selectors. * Even if the selector is valid, an exception will be thrown if nwsapi does not support it.
log: # selectors/selector/querySelectorAll # jsdom x 1.11 ops/sec ±4.85% (7 runs sampled)
The more errors there are, the shorter the processing time is, so I think it to be slower if it is tested on dom-selector. |
log: # selectors/selector/querySelectorAll # 18/273 fails. jsdom x 1.14 ops/sec ±5.54% (7 runs sampled)
Log:
|
Great! And what are the results for dom-selector? |
I haven't tested it yet. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good with nits; please fix those and then we'll merge. (I apologize, I might merge tomorrow, as I need to head to bed soon...)
Latest log:
|
Split from #3644
The reasons for using
try-catch
are:Benchmark result on my local PC is: