CQ claims massive 64-bit binary size growth - how to diagnose?

[Nate Chapin]

Hi binary-size@,

I'm a bit confused by the CQ dry-run output I'm getting, and I was looking for advice.

The CL in question is https://chromium-review.googlesource.com/c/chromium/src/+/5581408.

The "Android Binary Size" is what I'd expect. I'm adding 2 int16s to a constexpr data structure with a little over 1000 instances. That should lead to a 4-5k binary size increase, and that's what the superdiff results show.

But the "Android Binary Size (arm64 high end)" result is a 574k increase, which doesn't make any sense. I've been trying to follow the instructions to run diagnose_bloat.py locally, but can't seem to get it running for a 64-bit build. Any advice on how to get a breakdown of where this alleged massive increase is coming from (or how worried to be about it)?

Thanks!
~Nate

[Andrew Grieve]

I'll get on writing instructions for how to run diagnose_bloat.py against 64-bit.

In the meantime, here's the result for your CL: https://chrome-supersize.firebaseapp.com/viewer.html?load_url=https://storage.googleapis.com/chrome-supersize/private-oneoffs/352f14491a303e67ee9e86df0a02c5b26de57a54_4ec9e5fdc90c2052452f843122ca835f462580e2.sizediff

--
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/CACf%3D2LKYLnc9nR2fp4xSgJzZQydeEAnj1%2Ba9BPz%2BnO%2B%2BEtJwsw%40mail.gmail.com.

[Andrew Grieve]

Instructions added: https://chromium.googlesource.com/chromium/src/+/main/docs/speed/binary_size/android_binary_size_trybot.md#arm64-vs-arm32