search

JanitorTechnology / dockerfiles

popular development environments as containers
https://hub.docker.com/u/janitortechnology/
53 stars 20 forks source link

Chromium: use a faster preset #181

Closed ishitatsuyuki closed 6 years ago

ishitatsuyuki commented 6 years ago

With this preset build is 3x faster (3h -> 1h) and artifacts takes 1/4 space (26GiB -> 6GiB).

Jumbo: in general this is good for build speed. Slightly makes rebuild slower.

Reduced debug level: the debug information is function only as opposed to line-level. This may make debug harder but in general it's not a critical drawback.

Documents: https://chromium.googlesource.com/chromium/src/+/lkcr/docs/linux_build_instructions.md#faster-builds

jankeromnes commented 6 years ago

So cool, these are impressive time and space savings! Thanks! :+1:

Slightly makes rebuild slower.

Do you know how much slower? Does it impact how well incremental builds detects what needs to be rebuilt and what not?

@beaufortfrancois and @phistuck, do you know about use_jumbo_build=true and symbol_level=1? Would these options have any impact on your work if we enable them?

phistuck commented 6 years ago

@jankeromnes - for my purposes (mainly JavaScript changes in the Developer Tools), I do not think it would have any impact.

phistuck commented 6 years ago

@jankeromnes - any negative impact, I mean. :)

phistuck commented 6 years ago

@jankeromnes - but for C++ development/bug fixing, I imagine it would have a strong impact (debuggability is reduced).

ishitatsuyuki commented 6 years ago

Do you know how much slower? Does it impact how well incremental builds detects what needs to be rebuilt and what not?

More files is built into an object, so the rebuilt "unit" is larger now. That's all.

Regarding the debug level - I think it's a tradeoff; trying to be capable on all fields is expensive. Nobody could have been using debugger on Janitor yet, so we can only hear from those who work on Chromium locally.