- From: David Kuettel <kuettel@google.com>
- Date: Wed, 18 Mar 2015 17:09:33 -0700
- To: Chris Lilley <chris@w3.org>
- Cc: "public-webfonts-wg@w3.org" <public-webfonts-wg@w3.org>, "kenjibaheux@chromium.org" <kenjibaheux@chromium.org>
- Message-ID: <CAAYUqgF8xxR5mxL=OxxGf4gqwHm=GAiGpK_4s0=zLQBHpnqr7w@mail.gmail.com>
Thank you for updating the Evaluation Report Chris! On the topic of decompression performance, we have been tracking this to date with Action 116 (Decoder performance analysis on mobile devices), with a target of late April. https://www.w3.org/Fonts/WG/track/actions/116 The quick update is that Chrome (v42) has been instrumented to gather samples of both the WOFF 1.0 and WOFF 2.0 decode times, and now we are just waiting for the release to reach Stable. Once in wide use, we would be able to drill into the samples by device type (desktop, mobile, etc). We're all eagerly anticipating the results! On Wed, Mar 18, 2015 at 5:40 AM, Chris Lilley <chris@w3.org> wrote: > Hello, > > I have updated the editors draft of the WOFF2 evaluation report > http://www.w3.org/Fonts/WG/WOFF2ER/ > > Changes since first publication: > > Compression results for Adobe CFF and TTF corpi added to Appendix B > Discussion of compression results updated > Brotli IPR section updated to reflect ongoing standardization in IETF > References updated to latest versions > > Issues: > > I need something to put in there about memory usage for decompression. > Do we have more recent figures for decompression time? > > From the requirements: > http://www.w3.org/Fonts/WG/WOFF2ER/#req > > * Not take significantly longer than WOFF 1.0 to decompress > * Not take significantly more RAM than WOFF 1.0 to decompress > > compare the discussion for lzma > http://www.w3.org/Fonts/WG/WOFF2ER/#lzma-timespace > > with what I currently have for brotli > http://www.w3.org/Fonts/WG/WOFF2ER/#brotli-timespace > > -- > Best regards, > Chris Lilley, Technical Director, W3C Interaction Domain > > >
Received on Thursday, 19 March 2015 00:10:21 UTC