Closed Bug 580447 Opened 15 years ago Closed 15 years ago

Add a "file" function in the js shell

Categories

(Core :: JavaScript Engine, defect)

defect
Not set
minor

Tracking

()

RESOLVED INVALID

People

(Reporter: paul.biggar, Unassigned)

Details

Attachments

(1 file)

`file` reads the contents of a file to a JS string. The problem this solves is that reading from disk on linux is noisy (2-3%), and its making it difficult to tell if patches have any effect on the benchmark run-time. File allows separating reading from disk with evaling the code. The patch isn't ready for landing (see call to fread), but it's good enough to test this.
Benchmarks solve this problem by running a preliminary, unrecorded test to "pretty much ensure" that the requisite files are in cache for future runs. Is there any benchmark you specifically have in mind that requires re-reading from disk? Alternate idea: create a RAMdisk; run benchmarks from there.
We already have snarf, no need for another workalike. /be
(In reply to comment #2) > We already have snarf, no need for another workalike. Indeedy, I missed that. (In reply to comment #1) > Benchmarks solve this problem by running a preliminary, unrecorded test to > "pretty much ensure" that the requisite files are in cache for future runs. Is > there any benchmark you specifically have in mind that requires re-reading from > disk? No, I'm just getting very noisy benchmark results; sayre suggested disk io has an effect on linux. > Alternate idea: create a RAMdisk; run benchmarks from there. Great idea, will try that.
Status: NEW → UNCONFIRMED
Ever confirmed: false
See bug 580532 for more attempts to reduce variability.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: