New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 6 users

Issue metadata

Status: ----
Owner: ----
Cc:
Area: Font
NextAction: ----
Priority: Icebox
Type: Idea

Blocked on:
issue 1131



Sign in to add a comment
link

Issue 1132: Log glyph cache statistics to drive benchmark development

Reported by tomhud...@chromium.org, Feb 27 2013 Project Member

Issue description

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.
 

Comment 1 by tomhud...@chromium.org, Feb 27 2013

Project Member
Blockedon: skia:1131
Cc: bungeman@google.com caryclark@google.com reed@google.com
Labels: -Type-Defect Type-Enhancement
Summary: Log glyph cache statistics to drive benchmark development (was: Log glyph caceh )
If we interface to Chrome's UMA histograms (qv https://code.google.com/p/skia/issues/detail?id=1131), we can start collecting statistics on glyph cache usage in the wild.

Let's start with cache size and number of pages in use, if we can figure those out; other suggestions are welcome.

Comment 2 by tomhud...@chromium.org, Feb 27 2013

Project Member
Status: New
Chrome has a semi-redundant "glyph cache" in WebKit; we may not understand well enough how much of that is used and how it ties into the Skia glyph cache.

Right now two statistics are logged:
Memory.GlyphPagesPerLoad
WebCoreCache.FontsSizeKB

Comment 3 Deleted

Comment 4 Deleted

Comment 5 by hcm@google.com, Jul 16 2015

Project Member
Labels: -Priority-Medium Priority-Icebox

Comment 6 by tomhudson@google.com, Oct 5 2016

Project Member
Cc: hcm@google.com
Owner: ----
Status: (was: New)

Comment 7 by caryclark@google.com, Dec 17

Project Member
Cc: carycl...@skia.org

Comment 8 by caryclark@google.com, Dec 17

Project Member
Cc: -caryclark@google.com

Sign in to add a comment