Developers are spending more and more time of their days compiling.
How long is your build?
Printable View
Developers are spending more and more time of their days compiling.
How long is your build?
Is it kinda survey?
yes
We are? I would think as hardware becomes faster and multi-core processors are everywhere, we'd be spending less time compiling. How long a build takes depends on what I'm building and what language I'm working in.Quote:
Originally Posted by Incredibuild
7 min 16 sec 34 ms
Since moving to the new and faster build machine.
13 hours give or take for a complete regenerate and rebuild. (it used to be more than a day).
5 hours for a rebuild without regen.
10mins for a typical daily dev build.
A minute or so for the normal change code/debug type cycle.
13 hours... whoa. An operating system?
I really hope you guys enable the the /MP compiler option.
It used to have a lot of bugs, but multithreaded compilation is pure win with later versions of VS.
No, the regenerate is creating .cpp and .h files for internal data tables and the code for the solid state machine to process them. It basically has nothing to do with "compiling" other than that it spits out code that needs to be compiled. A preprocessor of sorts if you want to view it that way.
It's a "hardcoded" optimization process whereby we generate all possible decisions into tables so that each decision making step is just a handfull of instructions rather than a lot of complex calculations.
Once generated, it comes out at about 1420Mb worth of sources that gets compiled into static arrays totalling about 470Mb.
Compiling those takes the compiler a while (the bigger part of the 5hours) but only needs to happen once (until they change, which isn't frequent). actual code we work on regularly is fairly limited hence the 10min 'normal dev build' time.
NDA's mean I can't say much about it, but it's related to avionics.