[Webkit-unassigned] [Bug 158083] LLInt should support other types of prototype GetById caching.

[bugzilla-daemon at webkit.org]

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

--- Comment #35 from Caio Lima <ticaiolima at gmail.com> ---
(In reply to comment #34)
> (In reply to comment #32)
> > Created attachment 280573 [details]
> > 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"
> }
> ```

It is a nice information. BTW, How can I manage the DYLD_FRAMEWORK_PATH between 2 different builds?

-- 
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/20160606/c83554ea/attachment.html>