Closed
Bug 839450
Opened 12 years ago
Closed 11 years ago
Add Parsemark to the repo
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: n.nethercote, Assigned: n.nethercote)
Details
(Whiteboard: [js:t])
Attachments
(1 file)
1.94 MB,
application/x-gzip
|
Details |
cdleary created a parsing speed benchmark called Parsemark.
js/src/tests/parsemark.py is the script he used to run it. In my experience, the output of parsemark.py is extremely unreliable. For whatever reason, the times it measures have way too much noise. I think we should just delete it.
However, I have a copy of the benchmark that I modified so it could be used within the Sunspider harness. Each test has two files.
- A foo.data file, which contains the source code to parse.
- A foo.js file, which contains a single line like |parse(snarf("foo.data"));|.
I had success using it a while back (https://blog.mozilla.org/nnethercote/2011/07/01/faster-javascript-parsing/).
I've attached a gzip'd tarball of the test files. They can just be dropped into a Sunspider repo, under the tests/ directory, and then you can just use Sunspider's --suite option to run them.
It seems like this is something we should have in the repository. Any suggestions on where to put it? One difficulty is that it is 8 MB of source code...
![]() |
Assignee | |
Comment 1•11 years ago
|
||
This is going nowhere.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•