[Webkit-unassigned] [Bug 23050] New: Copying Fonts by value makes GraphicsContext::save() and restore() expensive
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue Dec 30 22:12:19 PST 2008
https://bugs.webkit.org/show_bug.cgi?id=23050
Summary: Copying Fonts by value makes GraphicsContext::save() and
restore() expensive
Product: WebKit
Version: 528+ (Nightly build)
Platform: Macintosh
OS/Version: Mac OS X 10.5
Status: NEW
Severity: Normal
Priority: P2
Component: Layout and Rendering
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: simon.fraser at apple.com
I have a Shark sample (generated from the testcase in bug 19312) that shows
that GraphicsContext::save() and restore() are pretty expensive; in this test.
they take 11.7% and 23% of the entire sample (of which 87% is in painting).
Focusing on GraphicsContext::restore(), GraphicsContext::operator= is 65%,
including 58% from Font::operator=. Vector::removeLast is 19%, and
restorePlatformState() is 14%. Of the Font::operator= cost, almost all is in
the GlyphPageTreeNode hash table copy.
Inside GraphicsContext::save(), 62% is in the Font constructor, and 22% is
savePlatformState.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the webkit-unassigned
mailing list