Though I don’t have specific numbers to share, WebKit2’s design generally provides much better performance under these conditions:
(1) Faster: Long-running JavaScript programs on iOS; (2) Faster and smoother: Scrolling; (3) Faster and smoother: More than one webpage open at once; (4) Less memory use: opening and closing many webpages over time. Geoff > On May 10, 2017, at 6:19 AM, Rodney Dowdall <[email protected]> > wrote: > > Hello > > We currently have a port of WebKit that uses the WebKit API. It works well, > but the performance isn't quite at the level of some other WebKit ports. > > I was wondering if there would be an expected performance gain by using the > Webkit2 API. My line of thinking is that the streamlining that takes place > under the WebKit API could be killing our performance. > > Are there any performance numbers that show if there is a difference between > the two API's? > > Thanks, > Rodney > -- > > Rodney Dowdall > Senior Software Developer > t. +1 (613) 595 1999 x513 <> > e. [email protected] <mailto:[email protected]> > <http://www.cranksoftware.com/> > w. www.cranksoftware.com <http://www.cranksoftware.com/> > > > _______________________________________________ > webkit-dev mailing list > [email protected] > https://lists.webkit.org/mailman/listinfo/webkit-dev
_______________________________________________ webkit-dev mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-dev
