[Webkit-unassigned] [Bug 156147] [JSC] implement async functions proposal

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sat May 28 06:14:58 PDT 2016


https://bugs.webkit.org/show_bug.cgi?id=156147

--- Comment #104 from Caitlin Potter (:caitp) <caitp at igalia.com> ---
(In reply to comment #103)
> (In reply to comment #97)
> > The dromaeo results for the latest patch are about 3-4% regressions for each
> > test. With the branch prediction adjustment, there's a 5-10% improvement (If
> > there's a command to dump results of run-perf-tests as text, I'll provide
> > all the numbers).
> > 
> > With the command `run-jsc-benchmarks --outer 10 --octane --benchmark
> > "closure|jquery" baseline:~/git/WebKit2/WebKitBuild/Release/DumpRenderTree
> > asyncawait:~/git/WebKit/WebKitBuild/Release/DumpRenderTree`, results are:
> > 
> >                          baseline                 asyncawait                
> > 
> > 
> > closure              0.30989+-0.00551          0.30340+-0.00295        
> > might be 1.0214x faster
> > jquery               3.65550+-0.01427    !     3.78112+-0.03262       !
> > definitely 1.0344x slower
> > 
> > <geometric>          1.06425+-0.01004    ?     1.07103+-0.00613       ?
> > might be 1.0064x slower
> > ---
> > 
> > The jquery results might look a little worse than previously described, but
> > the fact that Dromaeo consistently does so much better with the branch
> > predictions added goes a long way in my opinion.
> > 
> > Ensuring that `m_runtimeFlags` is packed efficiently and accessed in cache
> > more often will probably see some improvement, but hard to guess how much
> Are these the performance results of the patch that was just landed?
> Or is this the performance if we actually have the feature enabled?

Well, that's a good question. I assume DumpRenderTree doesn't boot up with all RuntimeFlags enabled (the way the way the jsc shell does). If it does, then that would incorporate the results of the feature if it were shipped

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160528/8f7aadbb/attachment.html>


More information about the webkit-unassigned mailing list