Open
Bug 1349148
Opened 8 years ago
Updated 7 months ago
Improve performance of megamorphic stubs
Categories
(Core :: JavaScript Engine: JIT, enhancement, P3)
Core
JavaScript Engine: JIT
Tracking
()
NEW
Performance Impact | low |
People
(Reporter: jandem, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: perf)
Some random ideas to consider/investigate:
* We could add a 1-entry cache to ShapeTable (both for hits and misses).
* We create a ShapeTable when there are more than 11 entries (ShapeTable::MIN_ENTRIES) but we should measure what the best value is for this nowadays. Since bug 1314569 we can purge ShapeTables on GC so we could be a bit more eager.
* Maybe when the number of entries is small, it would be faster for ShapeTable to store an array of {id, Shape*}.
* We could add a global cache/HashTable to avoid looking at each object on the proto chain.
Reporter | ||
Comment 1•8 years ago
|
||
* We should also check how common ShapeTable hash collisions are.
Updated•8 years ago
|
Whiteboard: [qf]
Updated•8 years ago
|
Whiteboard: [qf] → [qf:investigate]
Comment 2•6 years ago
|
||
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Comment 3•6 years ago
|
||
I can do some of these measurements, especially since I have the instrumentation already setup from bug 1384808.
Assignee: nobody → dpalmeiro
Flags: needinfo?(dpalmeiro)
Updated•4 years ago
|
Flags: needinfo?(dpalmeiro)
Updated•3 years ago
|
Assignee: dpalmeiro → nobody
Updated•3 years ago
|
Performance Impact: --- → ?
Whiteboard: [qf:investigate]
Updated•3 years ago
|
Performance Impact: ? → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•