Closed
Bug 1096807
Opened 10 years ago
Closed 8 years ago
Use fewer DataBuffers when parsing PathSegments
Categories
(Firefox Graveyard :: Shumway, defect, P3)
Firefox Graveyard
Shumway
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: mbx, Assigned: till)
References
Details
At the moment we seem to be creating a new DataBuffer for every path segment. DataBuffers are not very lightweight objects and we shouldn't create so many. In Zombotron 2 for instance, we parse nearly 283,135 such segments.
Assignee | ||
Comment 1•10 years ago
|
||
Yeah, that is the single biggest cause of slow parsing. I'll overhaul shape parsing after I land bug 1035170.
Status: NEW → ASSIGNED
Depends on: 1035170
Comment 2•10 years ago
|
||
Shape parsing is a bottleneck for fonts and vector graphics.
Blocks: shumway-m3
Priority: -- → P3
Summary: User fewer DataBuffers when parsing PathSegments. → Use fewer DataBuffers when parsing PathSegments
Assignee | ||
Comment 3•9 years ago
|
||
Parsing is much less of a bottleneck overall, but we should at least spend some effort on optimizing this before launch.
Updated•8 years ago
|
Product: Firefox → Firefox Graveyard
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•