Open Bug 642003 Opened 14 years ago Updated 2 years ago

[meta] Analyze v8 benchmark scores in detail

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Type:
defect

Tracking

()

People

(Reporter: dmandelin, Unassigned)

References

(Depends on 2 open bugs)

Details

(Keywords: meta)

We need to know what we need to do besides type inference here. What will GC fix and what do we need other work for?
Depends on: 642054
https://wiki.mozilla.org/V8bench_Info is a ready-made one-stop shop for holding info about v8bench. It would be great if what's learned could be put into that wiki page, so that the information isn't fragmented across a bunch of bugs.
(In reply to comment #1) > https://wiki.mozilla.org/V8bench_Info is a ready-made one-stop shop for holding > info about v8bench. It would be great if what's learned could be put into that > wiki page, so that the information isn't fragmented across a bunch of bugs. I'll add summaries there when I get a chance.
Depends on: 643565
Depends on: 643615
Depends on: 643639
Depends on: 643643
Depends on: 643646
(In reply to comment #2) > (In reply to comment #1) > > https://wiki.mozilla.org/V8bench_Info is a ready-made one-stop shop for holding > > info about v8bench. It would be great if what's learned could be put into that > > wiki page, so that the information isn't fragmented across a bunch of bugs. > > I'll add summaries there when I get a chance. OK, I've summarized my findings there.
Assignee: general → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.