New issue
Advanced search Search tips
Starred by 5 users
Status: ----
Owner: ----
Cc:
Area: Font
Priority: Icebox
Type: Idea

Blocked on:
issue 1131



Sign in to add a comment
Log glyph cache statistics to drive benchmark development
Project Member Reported by tomhud...@chromium.org, Feb 27 2013 Back to list
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.


 
Project Member Comment 1 by tomhud...@chromium.org, Feb 27 2013
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.
Project Member Comment 2 by tomhud...@chromium.org, Feb 27 2013
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
Project Member Comment 5 by hcm@google.com, Jul 16 2015
Labels: -Priority-Medium Priority-Icebox
Project Member Comment 6 by tomhudson@google.com, Oct 5 2016
Cc: hcm@google.com
Owner: ----
Status:
Sign in to add a comment