Tracking V8's compiled code size

[Andrew Grieve]

I've been looking at Chrome.apk size jumps via chromeperf (example), but often the commit that causes a non-trivial jump is a v8 roll.

Is anyone aware of a bot that tracks v8's size (maybe via d8) on a per-commit basis? Or if telemetry can be made to fill in the data for sub-roll commits?

[Ned]

+Simon Hatch 

On Tue, Jan 3, 2017 at 2:11 PM Andrew Grieve <agr...@chromium.org> wrote:

I've been looking at Chrome.apk size jumps via chromeperf (example), but often the commit that causes a non-trivial jump is a v8 roll.

Is anyone aware of a bot that tracks v8's size (maybe via d8) on a per-commit basis? Or if telemetry can be made to fill in the data for sub-roll commits?

--
You received this message because you are subscribed to the Google Groups "telemetry" group.
To unsubscribe from this group and stop receiving emails from it, send an email to telemetry+...@chromium.org.

[Simon Hatch]

Not aware of anything that tracks Chrome.apk on a per-commit basis for stuff like v8. The perf bots build on demand when bisecting into those, so you may be able to bisect a sudden size jump (I haven't tried it so I'm not sure if bisect will work out of the box here, don't see any reason it wouldn't though).

+Simon Hatch 

To unsubscribe from this group and stop receiving emails from it, send an email to telemetry+unsubscribe@chromium.org.

[Andrew Grieve]

The bisects seem to always fail. E.g.:

https://bugs.chromium.org/p/chromium/issues/detail?id=678309

That said, if they worked, that would probably be good enough. Certainly willing to file a bug for this if you know the components / owners?

[Simon Hatch]

Tests>AutoBisect

Me/dtu

[Andrew Grieve]

Filed https://bugs.chromium.org/p/chromium/issues/detail?id=678338