<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [JSC] implement async functions proposal"
href="https://bugs.webkit.org/show_bug.cgi?id=156147#c113">Comment # 113</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [JSC] implement async functions proposal"
href="https://bugs.webkit.org/show_bug.cgi?id=156147">bug 156147</a>
from <span class="vcard"><a class="email" href="mailto:utatane.tea@gmail.com" title="Yusuke Suzuki <utatane.tea@gmail.com>"> <span class="fn">Yusuke Suzuki</span></a>
</span></b>
<pre>The performance of the Parser.h / Parser.cpp reverted version is the following.
It gives us super nice insight that the cause of the code-load regression should reside in Parser.cpp's change.
Generating benchmark report at /home/yusukesuzuki/dev/WebKit/baseline_patched_Octane_hanayamata_20160529_0328_report.txt
And raw data at /home/yusukesuzuki/dev/WebKit/baseline_patched_Octane_hanayamata_20160529_0328.json
Benchmark report for Octane on hanayamata.
VMs tested:
"baseline" at /home/yusukesuzuki/dev/WebKit/WebKitBuild/old/Release/bin/jsc
"patched" at /home/yusukesuzuki/dev/WebKit/WebKitBuild/async/Release/bin/jsc
Collected 10 samples per benchmark/VM, with 10 VM invocations per benchmark. Emitted a call to
gc() between sample measurements. Used 1 benchmark iteration per VM invocation for warm-up. Used
the jsc-specific preciseTime() function to get microsecond-level timing. Reporting benchmark
execution times with 95% confidence intervals in milliseconds.
baseline patched
closure 0.62566+-0.00522 0.62292+-0.00696
jquery 8.03686+-0.02728 7.96035+-0.06515
<geometric> 2.24234+-0.00828 2.22676+-0.01878 might be 1.0070x faster</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>