Mac build size sometimes dips by ~4 MB

[Ryan Heise]

Hello!

On our Mac X86 builder, we're noticing that we occasionally get a blip where a build is 4MB smaller than other surrounding CLs. For more information, see https://bugs.chromium.org/p/chromium/issues/detail?id=1188323. 

Any ideas?

[Nico Weber]

Do you have any tools to see where the binary size goes? If so, which part gets smaller? Resources? Binary? Which parts of the binary?

--
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/07c48d33-584d-4bd8-a2fb-4accc7ff81ben%40chromium.org.

[John Chen]

The Mac build size is measured by simply running du -s -k 'Google Chrome.app'. Experimenting on my Mac showed that the OS is quite nondeterministic in deciding how much space to allocate for each file. Even when the file sizes are identical, the du command may end up showing quite different sizes. For example, from build 276503 to build 276504, an increase of over 4 MB was shown, but examining files from the two builds showed they are of very similar sizes.

I think the right measurement might be simply enumerating all files and adding up their sizes, instead of relying on du command.

On Tuesday, March 16, 2021 at 3:42:44 PM UTC-7 Nico Weber wrote:

Do you have any tools to see where the binary size goes? If so, which part gets smaller? Resources? Binary? Which parts of the binary?

On Tue, Mar 16, 2021 at 5:14 PM 'Ryan Heise' via binary-size <binar...@chromium.org> wrote:

Hello!

On our Mac X86 builder, we're noticing that we occasionally get a blip where a build is 4MB smaller than other surrounding CLs. For more information, see https://bugs.chromium.org/p/chromium/issues/detail?id=1188323. 

Any ideas?

--
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+unsubscribe@chromium.org.

[Nico Weber]

I have faint memories of `du` not being reliable on macOS, but I'm not sure if I'm making that up or if it's an actual memory.

...aha: https://bugs.chromium.org/p/chromium/issues/detail?id=1092056&q=thakis%20du%20size&can=1

For manually comparing directories, the built-in `opendiff` utility is useful. For drilling into a binary, I used https://github.com/nico/bloat long ago.

On Wed, Mar 17, 2021 at 4:14 PM John Chen <john...@chromium.org> wrote:

The Mac build size is measured by simply running du -s -k 'Google Chrome.app'. Experimenting on my Mac showed that the OS is quite nondeterministic in deciding how much space to allocate for each file. Even when the file sizes are identical, the du command may end up showing quite different sizes. For example, from build 276503 to build 276504, an increase of over 4 MB was shown, but examining files from the two builds showed they are of very similar sizes.

I think the right measurement might be simply enumerating all files and adding up their sizes, instead of relying on du command.

On Tuesday, March 16, 2021 at 3:42:44 PM UTC-7 Nico Weber wrote:

Do you have any tools to see where the binary size goes? If so, which part gets smaller? Resources? Binary? Which parts of the binary?

On Tue, Mar 16, 2021 at 5:14 PM 'Ryan Heise' via binary-size <binar...@chromium.org> wrote:

Hello!

On our Mac X86 builder, we're noticing that we occasionally get a blip where a build is 4MB smaller than other surrounding CLs. For more information, see https://bugs.chromium.org/p/chromium/issues/detail?id=1188323. 

Any ideas?

--
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.