Re: Opt-in String Audit

[Jakob Kummerow]

[Forwarding to v8-dev for visibility]

Interesting data. TL;DR: We have 5,300 strings in V8, totalling 206 KB of binary size (for comparison: that's 10% of Chrome's overall string data). Only a small fraction (330 / 17KB) is from messages.cc. Large buckets seem to be: printf-logging, tracing, profiling/counters. Not sure whether there's any low-hanging fruit; it's certainly more string data than I would have guessed.

See the link below if you'd like to know more.

On Mon, Oct 7, 2019 at 4:15 PM Andrew Grieve <agr...@chromium.org> wrote:

We've created a one-off SuperSize snapshot with native code string literals names as "string contents":

https://storage.googleapis.com/chrome-supersize/viewer.html?load_url=oneoffs%2Fvery-long-string-literals.ndjson&min_size=&include="

I found it pretty interesting to poke around and see what strings exists, so I thought I'd shared. Certainly if you're an owner of a section of the codebase, it might be nice if you could check for excessive strings.

You can filter by minimum size, and/or by regular expression (note that all names start and end with a double quote). E.g. here's all strings that contain ".cc" paths

This was made using target_os="android".

--
You received this message because you are subscribed to the Google Groups "binary-size" group.
To unsubscribe from this group and stop receiving emails from it, send an email to binary-size...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/binary-size/CABiQX1WofcVKz-2mB_r-gLhDxcg9Q0emWVFLTnfK9zvABP85-w%40mail.gmail.com.