Closed
Bug 492538
Opened 15 years ago
Closed 15 years ago
Use Google's v8 benchmark suite for performance testing
Categories
(Rhino Graveyard :: Core, enhancement)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rspeyer, Unassigned)
References
()
Details
Attachments
(1 file, 1 obsolete file)
443.29 KB,
patch
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.10) Gecko/2009042315 Firefox/3.0.10 Build Identifier: Rhino 1.7 release 2 2009 03 22 Include the performance benchmarks from v8. Reproducible: Always Provide benchmark tests so that we can check for performance improvements or regressions as the implementation progresses.
Comment 2•15 years ago
|
||
Great, thanks! Looking at http://v8.googlecode.com/svn/data/benchmarks/v4/run.html I see that the current version of the benchmark appears to include "Splay" but I don't see that test when I run from ant. Is it a different version of the benchmark?
Yes, it's currently based on v3. I'll upgrade it to v4 to include the splay tree test.
Version 4 of the v8 benchmark suite. The new splay.js file tests memory usage, and I had to increase the JVM memory to 256MB to avoid an OutOfMemory exception.
Attachment #376918 -
Attachment is obsolete: true
Comment 5•15 years ago
|
||
Committed, with minor modifications to make it easier to add other benchmarks in the future.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•