Investigate using ninja for non-windows builds

[hoyosjs]

Looking at build times in this query (sadly internal) Windows native builds are now 10-12 mins on avg, while the linux and linux-musl variants take at least double as much and macOS has a long tail. It would be worth investigating the wins of doing this all across the board.

Tagging subscribers to this area: @dotnet/area-system-threading-tasks
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Looking at build times in this query (sadly internal) Windows native builds are now 10-12 mins on avg, while the linux and linux-musl variants take at least double as much and macOS has a long tail. It would be worth investigating the wins of doing this all across the board.

Author:	hoyosjs
Assignees:	-
Labels:	area-System.Threading.Tasks, untriaged
Milestone:	-

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Looking at build times in this query (sadly internal) Windows native builds are now 10-12 mins on avg, while the linux and linux-musl variants take at least double as much and macOS has a long tail. It would be worth investigating the wins of doing this all across the board.

Author:	hoyosjs
Assignees:	-
Labels:	area-Infrastructure
Milestone:	-

[jkoritzinsky]

We already have the infrastructure in our builds to support using Ninja on non-Windows platforms. So we just need to investigate build throughput

[janvorli]

Running build of debug flavor of coreclr on a clean state of the repo with and without Ninja on my Linux devbox:

time src/coreclr/build-runtime.sh
real    5m18.566s
user    29m52.820s
sys     2m7.488s

time src/coreclr/build-runtime.sh -ninja
real    5m12.258s
user    29m37.416s
sys     2m1.352s

So the gain is mere 6 seconds (may as well be a noise)

[ViktorHofer]

That's a bummer. Would be good to collect data, especially on machines with less cores. @janvorli what's your setup?

[janvorli]

This is a very old device (the CPU was introduced in 2009) with 8 cores:

 lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                8
On-line CPU(s) list:   0-7
Thread(s) per core:    1
Core(s) per socket:    4
Socket(s):             2
NUMA node(s):          2
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 26
Model name:            Intel(R) Xeon(R) CPU           E5530  @ 2.40GHz
Stepping:              5
CPU MHz:               2394.094
BogoMIPS:              4787.89
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              8192K
NUMA node0 CPU(s):     0-3
NUMA node1 CPU(s):     4-7
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ssbd ibrs ibpb stibp kaiser tpr_shadow vnmi flexpriority ept vpid dtherm ida flush_l1d

[hoyosjs]

No idea what causes then the builds to be so slow. I know on Alpine we use a pretty old version of clang, but I am not convinced it'd be that.