3 ms·
> ... our CI still runs around 10 compute years per day! Am I reading this correctly? They were using 3650+ machines continuously just for CI?
by trulyme 5y ago
> ... our CI still runs around 10 compute years per day!
Am I reading this correctly? They were using 3650+ machines continuously just for CI?
- vletal 5y agoI hope that incremental complication will get to a point for some languages where a significant portion of this could be cached.
- moelf 5y agomore like 3650 cores/threads
- Thev00d00 5y agoCompiling C++ and Rust takes a lot of cycles
- glandium 5y agoCompiling is actually is tiny part of what runs on CI.
- dralley 5y agoI have to imagine that the vast majority of the CI time is spent rendering HTML and executing javascript on a wide variety of hardware and software combinations, and has nothing to do with compiling. Even the simplest possible support matrix would look like this: MacOSX ===> Monterray, Big Sur, Catalina ===> x86, Aarch64 Windows ===> 10, 11 ===> x64, Aarch64 ===> Intel CPU $(flavors), AMD CPU $(flavors) ===> Nvidia GPU $(flavors), AMD GPU $(flavors), Intel GPU $(flavors) And that's excluding Linux where the combinations get even crazier
- jcranmer 5y agoThe builds take about 10-20 minutes wallclock time, depending on platform. Each test job generally takes at least that long, and this is after being split into many, many, many jobs to make it go faster.
- anarazel 5y agoMultiple cores make that a lot less ridiculous... And tend to easily be usable do accelerate compilation and running parallel tests.