<div dir="ltr">2016-09-21 14:32 GMT+02:00 Carlos Garcia Campos <span dir="ltr"><<a href="mailto:cgarcia@igalia.com" target="_blank">cgarcia@igalia.com</a>></span>:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">El mié, 21-09-2016 a las 14:17 +0200, Jérémy Lal escribió:<br>
> 2016-09-21 13:54 GMT+02:00 Carlos Garcia Campos <<a href="mailto:cgarcia@igalia.com">cgarcia@igalia.com</a>>:<br>
> > El mié, 21-09-2016 a las 12:05 +0200, Jérémy Lal escribió:<br>
> > > I noticed version 2.14 is significantly slower to load several<br>
> > web<br>
> > > views one after another.<br>
> > ><br>
> > > By load time i mean the time between a call to<br>
> > > `webkit_web_view_load_uri()` and the first<br>
> > > WEBKIT_LOAD_STARTED change event.<br>
> > ><br>
> > > In version 2.12 it takes half a second for the first load and<br>
> > less<br>
> > > than 100ms<br>
> > > when loading more views.<br>
> > > in version 2.14 it always takes the same time.<br>
> ><br>
> > So, you mean it takes more time the first load on every web view,<br>
> > right? subsequents loads in the same web view are not slow, right?<br>
> ><br>
> > If that's the case, yes, it's somehow expected, there's more work<br>
> > to do<br>
> > know when setting up web views, the web process has to create the<br>
> > compositing thread and wait for it to start rendering.<br>
><br>
> Yes it is (much) faster to load again an url on an already "loaded"<br>
> web view.<br>
> Still, half a second seems to be an eternity.<br>
<br>
</span>Yes, we will try to improve that.<br>
<span class=""><br>
> I'm using webkitgtk quite a lot for server-side DOM "prerendering", a<br>
> bit like<br>
> what is chromium's headless branch for, and i wonder if it's<br>
> something<br>
> that is going to happen in webkitgtk as well (i.e. the ability to<br>
> just disable<br>
> any kind of graphic computations, let alone the ability to not use<br>
> gtk).<br>
<br>
</span>Yes, I don't see why not. For now you could try disabling accelerated<br>
compositing using WEBKIT_DISABLE_<wbr>COMPOSITING_MODE env var.<br></blockquote><div><br></div><div>Very useful for that server use case, the init overhead has dropped to < 100ms.</div><div><br></div><div>Jérémy</div></div><br></div></div>