slow ninja build

[Luigi Semenzato]

I posted this to infra-dev (to reduce spam) but received no replies,
let me try here. (Let me know if there are better avenues.)

----------

My current ninja chrome build is too slow to be usable (hours). I
have been following directions here:

https://chromium.googlesource.com/chromiumos/docs/+/master/simple_chrome_workflow.md

It's not a fresh checkout. I synced the sources to ToT. Then for
good measure I left and re-entered the sdk shell.

The instructions also say to run ninja like this:

ninja -C out_${SDK_BOARD}/Release -j500 -l 10 chrome

In the past, someone suggested I should use a much smaller number of
jobs. Should the instructions be updated? (Interactive
responsiveness may matter or not depending on the situation, and it
didn't in my case.)

Thanks!

[Mike Frysinger]

the -j500 option is there if you're using goma.  if you aren't using goma, then 500 is way too large.  so make sure goma is active.

-mike

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
    http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAA25o9SspKzKGnUn3%2B9zbf_B_uP3X3-5tgxUxXs3a%3DZMvsDaxw%40mail.gmail.com.

[Luigi Semenzato]

goma seems to be active. It's showing me running tasks at localhost:8089.

[Sunny Sachanandani]

Goma can fallback to local build if the compiler version associated with your checkout revision is too old. Let's continue this discussion on the internal goma-users mailing list.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAA25o9QXmefPH-M4De6B4LnzUnGCLNAhn%3D_yMTAMKMZtWuew-Q%40mail.gmail.com.

[Luigi Semenzato]

Thank you, I have posted the question to goma-users@.

[Lei Zhang]

I've also hit this issue with SimpleChrome. In my case, I am
specifically trying to build older revisions to track down a ChromeOS
only regression. I've added GOMA_DISABLED=1 to the environment and
removed -j500. I think that may be better than having Goma do local
fallback mode?

> To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAA25o9QLxyxg9bC2Vv%2B6LpjCH_NvkVcQ5soxpz0Kk-9HkD0Dog%40mail.gmail.com.
>