4 ms·
Comparing compile times is done rarely. I sometimes tried to google some comparisons, but didn't find much. For a typical 1,5 MLOC project my clean build times
by WildParser 5y ago
Comparing compile times is done rarely. I sometimes tried to google some comparisons, but didn't find much.
For a typical 1,5 MLOC project my clean build times are sitting around 40 seconds.
I think that's pretty good, but I don't think I have a way to improve it much. Without writing a compiler from scratch I think 10 seconds are out of reach for me...
- algo_trader 5y agoDo u think your company will consider cloud compiler if this is x5 faster? There issues such as latency, delta synchronizing, and tool versioning. But its doable. If u build such a service (pun intended!), the issues are probably cost and security.
- WildParser 5y agoImprovements in build-time are very valuable to me. But I'm not sure if a cloud would help me much. Synching can easily eat up 10s. Also my tools are very unique (including a parser that I wrote myself). To be faster than local a cloud would have to be massively overclocked - and I can already reach good results locally. For actual improvements I need a massive improvement in compiler technology (last time I looked there were just too many single-threaded bottlenecks in my build process). Nothing a cloud can solve for me. Security is one issue - but hackers will most likely only get confused when they try to understand what is going on - also costs I usually don't like...