Closed
Bug 1370891
Opened 7 years ago
Closed 7 years ago
Render blob images in the thread pool
Categories
(Core :: Graphics: WebRender, enhancement)
Core
Graphics: WebRender
Tracking
()
RESOLVED
FIXED
mozilla56
Tracking | Status | |
---|---|---|
firefox56 | --- | fixed |
People
(Reporter: nical, Assigned: nical)
Details
Attachments
(1 file)
12.81 KB,
patch
|
jrmuizel
:
review+
|
Details | Diff | Splinter Review |
We need to get this off the render backend thread at least.
Assignee | ||
Comment 1•7 years ago
|
||
This is very naive, there's certainly more efficient ways to dispatch and collect the jobs. I am not 100% certain yet this is correct with respect to how freetype and trheads work together, although the ft libraries are in TLS right now so it might just work. This will most likely become more interesting as we move fonts out of the recording and have to manage what font has been registered on which worker somehow.
Attachment #8875289 -
Flags: review?(jmuizelaar)
Comment 2•7 years ago
|
||
Comment on attachment 8875289 [details] [diff] [review] Us the rayon thread pool Review of attachment 8875289 [details] [diff] [review]: ----------------------------------------------------------------- ::: gfx/webrender_bindings/src/bindings.rs @@ +905,5 @@ > + register_thread_with_profiler(format!("WebRender:Worker#{}", idx)); > + }); > + > + let workers = Arc::new(rayon::ThreadPool::new(worker_config).unwrap()); > + Can we be reusing the thread pool we already have?
Attachment #8875289 -
Flags: review?(jmuizelaar) → review+
Assignee | ||
Comment 3•7 years ago
|
||
(In reply to Jeff Muizelaar [:jrmuizel] from comment #2) > Can we be reusing the thread pool we already have? Yes that's in the other patch from bug 1370879 (which is written on top of this one).
Pushed by nsilva@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/a61952d96c3f Render blob images in webrender's thread pool. r=jrmuizel
Comment 5•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/a61952d96c3f
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox56:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla56
You need to log in
before you can comment on or make changes to this bug.
Description
•