Startup traces (opening Clank to NTP) for component build are reliably ~2 MiB less then for non-component build.

=== Component build ===

use_goma = true
target_os = "android"
is_debug = false
symbol_level = 1
disable_incremental_isolated_processes = true
is_component_build = true
arm_use_thumb = false
enable_profiling = true

Size reported by native heap profiler: 7,242 KiB

=== Non-component build ===

use_goma = true
target_os = "android"
is_debug = false
symbol_level = 1
disable_incremental_isolated_processes = true
#is_component_build = true
arm_use_thumb = false
enable_profiling = true

Size reported by native heap profiler: 9,685 KiB


Originally I found the problem while trying to use base::debug::ScopedThreadHeapUsage in components_unittests in component build. In that setup ScopedThreadHeapUsage was reporting 16 bytes instead of ~500. Disabling component build fixed the issue.
 

Deleted: component-1.json.gz 281 KB

component-1.json.gz 281 KB Download

Deleted: component-2.json.gz 275 KB

component-2.json.gz 275 KB Download

Deleted: non-component-1.json.gz 362 KB

non-component-1.json.gz 362 KB Download

Deleted: non-component-2.json.gz 363 KB

non-component-2.json.gz 363 KB Download