<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - LLInt should support other types of prototype GetById caching."
href="https://bugs.webkit.org/show_bug.cgi?id=158083#c35">Comment # 35</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - LLInt should support other types of prototype GetById caching."
href="https://bugs.webkit.org/show_bug.cgi?id=158083">bug 158083</a>
from <span class="vcard"><a class="email" href="mailto:ticaiolima@gmail.com" title="Caio Lima <ticaiolima@gmail.com>"> <span class="fn">Caio Lima</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=158083#c34">comment #34</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=158083#c32">comment #32</a>)
> > Created <span class=""><a href="attachment.cgi?id=280573" name="attach_280573" title="Cached Accessor's benchmark output">attachment 280573</a> <a href="attachment.cgi?id=280573&action=edit" title="Cached Accessor's benchmark output">[details]</a></span>
> > Cached Accessor's benchmark output
>
> You can compare two VMs directly using the `run-jsc-benchmarks` script. This
> will give you nice output showing the differences so you don't have to
> manually compare the results.
> Like so:
> `run-jsc-benchmarks baseline:<pathToBaslineBuild>/jsc
> changes:<pathToChanges>/jsc`
>
> You can run individual benchmarks like (this runs only Kraken):
> `run-jsc-benchmarks --kraken baseline:<pathToBaslineBuild>/jsc
> changes:<pathToChanges>/jsc`
>
> You can make run-jsc-benchmarks run more iterations which is helpful for
> noisy benchmarks. The default is 4 runs. This will make kraken run for 10
> runs:
> `run-jsc-benchmarks --kraken --outer 10 baseline:<pathToBaslineBuild>/jsc
> changes:<pathToChanges>/jsc`
>
> You can also provide a regex to specify sub tests inside a benchmark suite.
> This will run just ai-astar and audio-fft from kraken.
> `run-jsc-benchmarks --kraken --benchmarks "ai-astar|audio-fft"
> baseline:<pathToBaslineBuild>/jsc changes:<pathToChanges>/jsc`
>
>
> Also, you should get yourself an Octane and Kraken. They can be found on
> github I think. We don't bundle those benchmarks inside WebKit itself, but
> run-jsc-benchmarks
> will look for the following the following JSON file:
> `~/.run-jsc-benchmarks`
> Which specifies paths to where Octane/Kraken can be found.
>
> My `~/.run-jsc-benchmarks` looks like:
> ```
> {
> "OctanePath": "/Volumes/Data/jsc-benchmarks/octane",
> "KrakenPath": "/Volumes/Data/jsc-benchmarks/kraken/tests/kraken-1.1"
> }
> ```</span >
It is a nice information. BTW, How can I manage the DYLD_FRAMEWORK_PATH between 2 different builds?</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>