Unexpected sizes: Uncompressed growth is exactly half of compressed growth

[Leo Zhao]

I am working on a Bling iOS project that requires moving code from `content` to `components` so it can be shared.

This tryjob, chromium/try/fuchsia-binary-size,  is failing with some unexpected numbers:

Size check failed! The following package(s) are affected:
- web_engine (compressed) grew by 16384 bytes (uncompressed growth: 8192 bytes).
Note that this bot compares growth against trunk, and is not aware of CL chaining.
- chrome_fuchsia (compressed) grew by 16384 bytes (uncompressed growth: 8192 bytes).
Note that this bot compares growth against trunk, and is not aware of CL chaining.

First, shouldn't the compressed bytes smaller than uncompressed growth? Second, the grew-by numbers are exactly 2x of the uncompressed growth. The number is too pretty, 8192, exactly 8K. Are there any concerns about those numbers?

In case you may want to see the original message, here is the link: 

https://ci.chromium.org/ui/p/chromium/builders/try/fuchsia-binary-size/1367534/overview

This is the CL that triggers it:
https://chromium-review.googlesource.com/c/chromium/src/+/7206691

Thanks
Leo Zhao

[Daniel Bratell]

Programs, and binaries, often work in "blocks", historically often 4k, but sometimes larger. I don't know fuchsia but it's probably using 4-8k blocks from what you list.

What I see in your numbers is that some files have grown 1, 2 or maybe 4 blocks. That is often within noise levels so unless I specifically worried about the size of a change, I would not worry. If you want to know more exactly, you need to dig in to find exactly what has grown and by how much.

As for growing 16 KB in the compressed version when the compressed version only grew 8k, that is a bit unusual, but since we're talking about 1, 2 or possibly 4 blocks, I would probably dismiss it as a result of unfortunate rounding.

/Daniel

--
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 visit https://groups.google.com/a/chromium.org/d/msgid/binary-size/c89cd66e-dcc5-418f-8710-6c9f3f42ebfan%40chromium.org.