fix(producer): skip slow TTC recompression#2322
Open
miguel-heygen wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Skip wawoff2 recompression for TTC font collections and embed them as raw font/collection data URIs with the matching CSS format(collection) hint.
Why
A reported 120-second talking-head package spent about six extra minutes compiling a TTC font. Reproduction with a 19 MB Noto Sans CJK collection took 57.73 seconds and about 320 MB RSS in fontToDataUri alone. Chromium also rejects a raw collection when it is mislabeled as format(woff2).
How
The same real TTC now embeds in 0.07 seconds with the correct data URI prefix.
Test plan