Compilation is taking a ton of memory
Shachar Shemesh
shachar at weka.io
Sun Jul 1 06:55:42 UTC 2018
On 28/06/18 01:46, Steven Schveighoffer wrote:
> This has been a thorn in many sides for a long time. I remember
> Weka.io's Liran talking about how they required an INSANE amount of
> time/memory to build their system in dconf 2015 maybe? But things have
> gotten a bit better since then. I think at some point there will be a
> reckoning where it has to be fixed. Fast compile-time is cool, but
> inifinte compile time (i.e. it never finishes because the OOM killer
> destroys your process) is not acceptable.
No, we just use bigger build servers:
$ cat /proc/cpuinfo
...
processor : 127
vendor_id : GenuineIntel
cpu family : 6
model : 63
model name : Intel(R) Xeon(R) CPU E7-8880 v3 @ 2.30GHz
stepping : 4
microcode : 0x11
cpu MHz : 2300.072
cache size : 46080 KB
physical id : 3
siblings : 32
core id : 15
cpu cores : 16
apicid : 223
initial apicid : 223
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx pdpe1gb
rdtscp lm constant_tsc arch_perfmon rep_good nopl xtopology nonstop_tsc
aperfmperf eagerfpu pni pclmulqdq monitor est ssse3 fma cx16 pcid sse4_1
sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand
hypervisor lahf_lm abm ida xsaveopt fsgsbase bmi1 hle avx2 smep bmi2
erms invpcid rtm
bogomips : 4662.97
clflush size : 64
cache_alignment : 64
address sizes : 46 bits physical, 48 bits virtual
power management:
ubuntu at ip-172-31-14-32:~$ cat /proc/meminfo
MemTotal: 2014743200 kB
My laptop has 32GB of ram. If I do single threaded compilation and
allocate enough swap, I can *barely* squeeze through a debug build
compilation of the node.
Shachar
More information about the Digitalmars-d
mailing list