1324250 - stylo: Use a global thread pool, instead of one per document.

Status: RESOLVED FIXED

(Core :: CSS Parsing and Computation, defect)

Description

[Emilio Cobos Álvarez (:emilio)]

Right now stylo spawns a thread pool per document it styles. That can be pretty inefficient and memory-consuming.

We should switch to use one global thread pool, and use that for all the documents we style.

This is probably easier with the scoped TLS stuff Bobby is working on right now.

Comment 1

[Chris Peterson [:cpeterson]]

Emilio, you should probably coordinate with billm about the Quantum DOM team's plans for task scheduling and prioritization. To be effective, a global thread pool would need to know about all threads, Rust/Rayon and C++, and task priorities.

Comment 2

[Xidorn Quan [:xidorn] UTC+11]

That is probably not necessary, because we block the main thread while doing restyling, and thus it is just about not creating too many thread pools. There is nothing to do with scheduling between different documents which are basically all run in the main thread.

Comment 3

[Emilio Cobos Álvarez (:emilio)]

Yeah, what Xidorn said, a single stylo thread pool per process is probably acceptable.

If that ends up being not acceptable we may want to figure out a way to reuse other thread pools around, but that'd be a big effort that is probably not worth without a clear reason.

Comment 4

[Bobby Holley (:bholley)]

We should be able to able to spin up the appropriate thread pool somewhere in nsLayoutStatics::Initialize.

NI Manish, who was looking for things to do. :-)

Comment 5

[Bobby Holley (:bholley)]

This was fixed in https://github.com/servo/servo/pull/15535