Skip to content

Add criterion.rs to html5ever/xml5ever #360

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

Merged
merged 8 commits into from
Dec 14, 2018
Merged

Conversation

Ygg01
Copy link
Contributor

@Ygg01 Ygg01 commented Dec 12, 2018

Fixes #45 and is a stepping stone for #286.

Why is this important for #286?

It allows project to track it's performance, since criterion.rs generates benchmark data and tracks changes to performance.

Possible enhancements

This is first pass at criterion. It's possible the performance could be better tracked, with more generic benchmarks.

Possibly publishing this data, to see how it behaves overall.

More tests for xml5ever, possibly tests that stress namespace rules and parts where xml is weak.

@Ygg01
Copy link
Contributor Author

Ygg01 commented Dec 13, 2018

@jdm @SimonSapin Should I separate this PR into two PRs?

Right now, inside this PR there is a pretty large, overhaul to x5e interface. Mainly to support speculative parsing, but I did it mostly, for interface parity.

Added additional dependcies, plus changed xml5ever interface in a major way.
Remove code reported as dead from benches.
1. Change String builder with `format!` macro
2. Replace parameter passing with just setting tokenization options to `Default`
@jdm
Copy link
Member

jdm commented Dec 14, 2018

@bors-servo r+

@bors-servo
Copy link
Contributor

📌 Commit b8e9bed has been approved by jdm

@bors-servo
Copy link
Contributor

⌛ Testing commit b8e9bed with merge d6b3beb...

bors-servo pushed a commit that referenced this pull request Dec 14, 2018
Add criterion.rs to html5ever/xml5ever

Fixes #45 and is a stepping stone for #286.

Why is this important for #286?
-----
It allows project to track it's performance, since [criterion.rs](https://github.com/bheisler/criterion.rs) generates benchmark data and tracks changes to performance.

Possible enhancements
-----
This is first pass at criterion. It's possible the performance could be better tracked, with more generic benchmarks.

Possibly publishing this data, to see how it behaves overall.

More tests for xml5ever, possibly tests that stress namespace rules and parts where xml is weak.
@bors-servo
Copy link
Contributor

☀️ Test successful - status-travis
Approved by: jdm
Pushing d6b3beb to master...

@bors-servo bors-servo merged commit b8e9bed into servo:master Dec 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants