Reducing build times of ldc-build-runtime

Jacob Carlborg doob at
Wed Mar 18 16:10:43 UTC 2020

On 2020-03-17 22:33, kinke wrote:

> The regular libs are built all-at-once (by default), but the unittests 
> require separate compilation (otherwise you need something like 24 GB of 
> RAM). With ninja, you're using parallelization by default, but I'd still 
> recommend to set the number of parallel jobs explicitly in the 
> ldc-build-runtime cmdline. Each job should have about 2 GB of memory. 
> What are the hardware specs for bitrise?

Not great:

Processor Speed: 2.58 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache (per Core): 256 KB
L3 Cache: 30 MB
Memory: 4 GB

> Sure, if the release unittests take too long to compile, then go ahead 
> and exclude them for now. A simple variant is to invoke 
> ldc-build-runtime as usual, but without `--testrunners`, and instead 
> invoke `ninja -j<N> druntime-test-runner-debug 
> phobos2-test-runner-debug` manually in the ldc-build-runtime.tmp directory.

I'll give that a try. Thanks.

> Yeah, 45 minutes is pretty short (and 11 minutes to compile LDC very 
> slow). An x86 simulator for Azure CI or so would be pretty much 
> unrestricted (6h time-out...).

Yeah. This is what you get in the free open source plan.

/Jacob Carlborg

More information about the digitalmars-d-ldc mailing list