Lars and I are moving the Servo buildmaster from Linode to AWS this week.
I'll change the build.servo.org DNS around 9am PST on Wednesday 3/30. If
all DNS servers behave correctly, build.servo.org should be down for no
longer than 5 minutes. After the transition, logs from builds completed on
the o
On Monday, March 21, 2016 at 11:45:06 AM UTC-5, Jack Moffitt wrote:
> I propose the following straw man transition plan:
>
> 1. Keep -c, -g, -w command line options as they are, but switch the
> default setting to WebRender.
> 2. Remove -g.
> 3. Add in an llvmpipe software-only fallback and replac
In general, does the software-fallback path for WebRender mean "really
really slow"? If WebRender avoids dirty-rects on the grounds that painting
is free, then a GL-based software path is going to be a lot slower than a
classic software rendering path.
On Mon, Mar 28, 2016 at 10:33 AM, wrote:
>
Last time I tried it, Servo with LLVMpipe and WR wasn't too bad, even on
the moire demo. It was slightly worse than Servo without WR, which IIRC has
similar performance as Gecko.
-Manish Goregaokar
On Tue, Mar 29, 2016 at 2:20 AM, Bobby Holley wrote:
> In general, does the software-fallback pat
There was no agenda to discuss, so we'll forgo today's meeting. See
you all in IRC :)
jack.
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
Keep in mind that Servo without WR doesn't do dirty rects and invalidation
either. (I had patches to do it but they weren't complete and bitrotted.)
The question in my mind is whether it'd be better to build the CPU fallback
on top of WebRender or whether it's best to build it on top of Skia. Ther
On Mon, Mar 28, 2016 at 3:06 PM, Patrick Walton wrote:
> Keep in mind that Servo without WR doesn't do dirty rects and invalidation
> either. (I had patches to do it but they weren't complete and bitrotted.)
>
Ok, so that helps to explain Manish's results above.
> The question in my mind is wh
7 matches
Mail list logo
