Plays via YouTube's privacy-enhanced embed

Fastest browser engine by far at 500 FPS! Servo Webrender - CSS on the GPU part 1: Rust

Name: Fastest browser engine by far at 500 FPS! Servo Webrender - CSS on the GPU part 1: Rust
Description: An excerpt from a Bay Area Rust meetup on Servo's WebRender, which renders CSS display lists on the GPU at very high frame rates. It explains the approach and demos rendering at around 500 FPS.

𝓖𝓷𝓸𝓶𝓮💫𝓢𝓪𝓷𝓮

Talks

YouTube

1 HN user recommended this talk1 month2017 score 1

Years with an HN recommendation, 2007–2026

HN commenters point to it when discussing how WebRender works and as evidence of what GPU-based browser rendering can achieve.

An excerpt from a Bay Area Rust meetup on Servo's WebRender, which renders CSS display lists on the GPU at very high frame rates. It explains the approach and demos rendering at around 500 FPS.

“If you have the time there is a nice talk about WebRender” (HN, 2017)

1 recommendations · 4 citations · Talks · intermediate · partly dated

Web development C, C++, Rust, Go & systems languages Computer graphics & rendering Talks Software Engineering & Languages

5 Hacker News comments

From the HN archive; up to 20 kept per video, favoring different commenters. Recommendations first.

@NiLSPACE Apr 2017 Recommends

on HN thread Mozilla and Microsoft are rebuilding their browsers’ foundations

If you have the time there is a nice talk about WebRender: [this video] Here is another great talk: [link] At ~25:30 he'll also talk a bit about Quantum. In a nutshell WebRender is used to send a web page to the GPU which will paint all divs, borders, shadows, images etc. Currently WebRender is the only component I'm aware of that is inside Firefox Nightly. It's still behind a config though.

Talk explaining how WebRender sends pages to the GPU.

View on Hacker News

Citations, criticism and jokes

@ZenoArrow Jan 2017 Cites it

on HN thread Transitioning Firefox's rendering engine from Gecko to Servo

>"If performance is not competitive" I don't think this will be a problem. One example... [this video] [link]

Demo of Servo WebRender rendering at very high frame rates.

View on Hacker News

@littlestymaar Sep 2017 Cites it

on HN thread CSS Triggers

You should take these advices with a grain of salt because it refers to the legacy rendering pipeline used by current web browers. There is not absolute rule stating that layout and painting must be slow while compositing is not. In fact Mozillians are currently working on a new rendering pipeline[1] based on state of the art rendering tools[2]. This new pipeline should be deployed in firefox in 2018 as a part of the ongoing Quantum project. [1] [link] [2] [this video]

Example of state of the art GPU rendering tools in Mozilla's new pipeline.

View on Hacker News

@yazaddaruvala Sep 2017 Cites it

on HN thread Introduction to WebRender

I'm sure the future blog posts will have more details, but it has to do with immediate mode vs retained mode APIs. [this video]

Explains immediate mode versus retained mode rendering.

View on Hacker News

@srcmap Nov 2017 Cites it

on HN thread Desktop compositing latency is real

According to this: [this video] Firefox's servo engine can compose CSS elements/Display List together at 500 frames / second. Maybe next version of Windows / Linux desktop should use FF's servo engine?

Shows Servo composing CSS display lists at 500 frames per second.

View on Hacker News