3 ms·
Do you know of a build system that can handle a source tree as large as an entire web browser without spawning a lot of processes? It's hard to tell what, if a
by wtallis 8y ago
Do you know of a build system that can handle a source tree as large as an entire web browser without spawning a lot of processes?
It's hard to tell what, if anything, you are recommending here. Pass thousands of files to a single compiler invocation? Ignore the problems and stop trying to make process creation and clean-up faster?
- im3w1l 8y ago> Pass thousands of files to a single compiler invocation? Sure. Or pass it a file with all the filenames. Or have the compiler work as a server that takes compilation requests over a socket. It's not like passing thousands of filenames between two processes is a deep unsolved problem.
- gpderetta 8y agoOr just spawn thousands of processes which has been done for the last 40 years without particular issues.
- mannykannot 8y agoSo, the solution to concurrency problems is to serialize everything?
- deleted 8y ago[deleted]
- fit2rule 8y ago"Concurrency is everything serialised, properly."
- mannykannot 8y agoThe posts we are replying to here seem to have a very narrow concept of what 'properly' entails in this case.
- xtrapolate 8y ago> "It's hard to tell what, if anything, you are recommending here." I don't think it's that hard to tell, you're simply ignoring what's been clearly written. So I'll quote it again and hope this time you'll actually read my comment: > "Start re-evaluating the entire pipeline and the practices employed". I've worked on several of projects far exceeding the size of "an entire web browser". You're taking the status quo for what it is. I'm asking questions. Are they employing caching of binaries/object files? Are they running a continuous build? Which parts of the build actually take the most time to go through? Can they benefit from building concurrently on multiple machines?
- Dylan16807 8y ago> Are they employing caching of binaries/object files? Are they running a continuous build? Which parts of the build actually take the most time to go through? Can they benefit from building concurrently on multiple machines? So you're suggesting things they already do. And if you're using multiple machines, you probably want to max out each machine, so it matters a lot if there's code that falls over and dies when applied to a large number of cores.