The PR to enable testing Webrender on the CI machines against OSMesa has
landed (https://github.com/servo/servo/pull/13382).
This should have no effect on most people.
However, we may start seeing some different and seemingly unrelated
intermittent failures, due to the different timing of the
TL;DR - We've merged the initial parts of WebRender2. Do expect some
regressions. Don't expect major performance wins (yet). Do expect some
major feature and performance improvements over the next few weeks.
Thanks to help from a number of people (esp. pcwalton, mchang,
mrobinson, nox and
Well, the idea here is to test the case in which the object isn't layerized
for some reason--say, the object was moving by animating "margin-left" in
JavaScript and it had complex Z-ordering constraints that caused whatever
layerization heuristics the browser had to fail, causing a full repaint of
This sounds very promising!
A question: one of the graphs shows Servo taking 35ms per frame to paint
the slide-in animation. What exactly is in this animation that makes it
take such a relatively long time to paint?
Rob
--
lbir ye,ea yer.tnietoehr rdn rdsme,anea lurpr edna e hnysnenh hhe
It's a fairly simple off canvas menu - it is full height (1024px in this
test), and expands from off-screen to 600px wide. It has a linear
gradient for the background, and a small amount of text on it.
I was also surprised the existing Servo paint code is so slow with this
- it's on my todo
5 matches
Mail list logo
