Re: [dev-servo] when to switch to webrender by default

2016-05-05 Thread Patrick Walton
I'm pretty sure auto fallback would be doable. Patrick On Wed, May 4, 2016 at 1:31 PM, Jack Moffitt wrote: > > So is the idea that people without the ability to use webrender would > need > > to use the -c flag? The linux machine I use for Servo development yields > the > > "GL context creation

Re: [dev-servo] when to switch to webrender by default

2016-05-04 Thread Jack Moffitt
> So is the idea that people without the ability to use webrender would need > to use the -c flag? The linux machine I use for Servo development yields the > "GL context creation failed" error, so if there were a way to make this > happen transparently that would be pretty great. Yes. I expect the

Re: [dev-servo] when to switch to webrender by default

2016-05-04 Thread Josh Matthews
On 2016-03-21 12:45 PM, Jack Moffitt wrote: Now that WebRender has landed and been tested a bit, I'd like to start a discussion of when to switch to this backend as our default. Are there issues that people see as blockers to this? If possible, I'd like to do this sometime in Q2. I propose the f

Re: [dev-servo] when to switch to webrender by default

2016-04-15 Thread Jack Moffitt
On Mon, Mar 28, 2016 at 11:33 AM, wrote: > 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. Ad

Re: [dev-servo] when to switch to webrender by default

2016-03-28 Thread Bobby Holley
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

Re: [dev-servo] when to switch to webrender by default

2016-03-28 Thread Patrick Walton
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

Re: [dev-servo] when to switch to webrender by default

2016-03-28 Thread Manish Goregaokar
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

Re: [dev-servo] when to switch to webrender by default

2016-03-28 Thread Bobby Holley
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: >

Re: [dev-servo] when to switch to webrender by default

2016-03-28 Thread lbergstrom
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

[dev-servo] when to switch to webrender by default

2016-03-21 Thread Jack Moffitt
Now that WebRender has landed and been tested a bit, I'd like to start a discussion of when to switch to this backend as our default. Are there issues that people see as blockers to this? If possible, I'd like to do this sometime in Q2. I propose the following straw man transition plan: 1. Keep -