diff options
| author | bors-servo <release+servo@mozilla.com> | 2013-10-31 23:25:26 -0700 |
|---|---|---|
| committer | bors-servo <release+servo@mozilla.com> | 2013-10-31 23:25:26 -0700 |
| commit | ddce8b8fa0b09f1d56ce9684028e23f4974b2e5f (patch) | |
| tree | 948bc835efe92c8acf61148113535e4082716ffb /src/components/style/errors.rs | |
| parent | a72d0558006b42bf9c697702057911bd45e102bf (diff) | |
| parent | 901dfc45e5ed2e0506a18488be69e083fd59501f (diff) | |
| download | servo-ddce8b8fa0b09f1d56ce9684028e23f4974b2e5f.tar.gz servo-ddce8b8fa0b09f1d56ce9684028e23f4974b2e5f.zip | |
auto merge of #1152 : ILyoan/servo/parallel_selector_matching, r=SimonSapin
This an attempt to parallelize selector matching.
Approach
* Let the `match_subtree` spawn limited number of tasks.
* Each of them takes a list of nodes that is uniformly distributed
* And then each task does the selector matching for every single node in its list.
(Not sure if this is worthwhile for long term especially considering CSS optimizing techniques such as ancestor filter or style sharing)
Benchmark from my machine (LayoutSelectorMatchCategory) (intel i7 3.4GHz * 8, linux x86_64)
* src/test/demo.html
* original: 0.07ms
* parallel: 0.20ms
* perf-rainbow.html
* original: 485ms
* parallel: 245ms
* A test page with 15000 nodes and 3000 CSS selector(including inline style).
* original: 140ms
* parallel: 60ms
Diffstat (limited to 'src/components/style/errors.rs')
0 files changed, 0 insertions, 0 deletions