Closed
Bug 1147683
Opened 9 years ago
Closed 9 years ago
Consider choosing a good inline capacity for DeserializedNode::EdgeVector
Categories
(DevTools :: Memory, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: fitzgen, Assigned: fitzgen)
References
Details
> ::: toolkit/devtools/server/DeserializedNode.h
> @@ +51,5 @@
> > +
> > +// A `DeserializedNode` is a node in the heap graph that we deserialized from a
> > +// core dump.
> > +struct DeserializedNode {
> > + using EdgeVector = Vector<DeserializedEdge>;
>
> Here is a case where choosing a good MinInlineCapacity (second template arg)
> could make a big difference. But let's get data first.
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → nfitzgerald
Assignee | ||
Comment 1•9 years ago
|
||
Took the average for each inline capacity N over 50 runs reading the same full process heap snapshot of one tab loaded to cnn.com: N | Avg. Time (ms) ---+--------------- 0 | 1815.10 1 | 1878.76 2 | 1907.86 3 | 1943.66 4 | 1887.62 6 | 1874.02 8 | 1935.78 16 | 2002.17 I don't think there is anything to do here.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•