Closed Bug 1345691 Opened 8 years ago Closed 6 years ago

stylo: Consider using sequential traversal for smaller subtrees

Categories

(Core :: CSS Parsing and Computation, enhancement, P4)

Product:
Core
Component:
CSS Parsing and Computation
Type:
enhancement

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox57 --- wontfix

People

(Reporter: bholley, Unassigned)

References

(Blocks 1 open bug)

Details

There's some analysis of optimal DOM size for parallel traversal in [1] and [2], though I think that's generally targeted at parallel layout. Servo has also landed something like this. With work stealing, we don't pay a huge cost for the parallel traversal, though we still have to context-switch to a worker thread. We already skip the full traversal machinery if there's no work to be done. It's not obvious to me how big of a problem this is going to be in practice. This is probably low priority until we have data that suggests otherwise - I'm just getting it on file. [1] https://github.com/servo/servo/issues/10110#issuecomment-215502694 [2] A more-detail paper that I have in my email somewhere
status-firefox57=wontfix unless someone thinks this bug should block 57
status-firefox57: --- → wontfix

We do this now.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.