android - How does Chrome's glyph cache work? -
thanks new chrome experimental profiler, i'm getting more info canvas2d app i'm developing. glyph cache memory usage massive, can see below :
i suspect 1 of reasons why it's doing i'm drawing each character 1 1 along path (because firefox supports text along path). each character added glyph cache, making memory usage ginormous , rendering speeds slow hell.
it worrying in android, i'm working on limited resources. app unusable unless don't render text way.
this article suggests using little offscreen canvases , drawimage
calls improves performance lot, 2 years ago.
so, how chrome's glyph cache work? cache each character, each word, each string passed filltext
? cache character or tuple of (character, size)
?
android html5 google-chrome canvas
No comments:
Post a Comment