On Tue, Oct 15, 2019 12:05:57 +0200, Dan Horák wrote:
On Mon, 14 Oct 2019 16:50:31 +0100
Ankur Sinha <sanjay.ankur(a)gmail.com> wrote:
> Hello,
>
> I'm working on packaging up graph-tool[1] for SciTech/NeuroFedora. The
> spec file is a WIP here[2]. I've not yet managed to complete a
> build---it managed to get my F31 server machine to go completely
> unresponsive when I had tried last evening---used up all the memory
> (32G) and most of the swap (15G). Upstream documents that they make
> heavy use of templates[3], and so the builds take quite a bit of time.
>
> My scratch build here has been running for ~7 hours now[4]. Any
> tips/tricks on speeding up the build?
how many CPUs are in the server?
This is what the koji build is running on (for 14 hours now):
https://koji.fedoraproject.org/koji/taskinfo?taskID=38295706
CPU info:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 6
On-line CPU(s) list: 0-5
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 6
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 60
Model name: Intel Core Processor (Haswell, no TSX, IBRS)
Stepping: 1
CPU MHz: 2299.996
BogoMIPS: 4599.99
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 32K
L1i cache: 32K
L2 cache: 4096K
L3 cache: 16384K
NUMA node0 CPU(s): 0-5
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc rep_good nopl xtopology
cpuid tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt
tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm invpcid_single pti
ibrs ibpb fsgsbase bmi1 avx2 smep bmi2 erms invpcid xsaveopt arat
Memory:
total used free shared buff/cache available
Mem: 15385888 722316 8003904 76 6659668 14321956
Swap: 134216700 120520 134096180
Storage:
Filesystem Size Used Avail Use% Mounted on
/dev/vda1 135G 41G 88G 32% /
the usual trick is to reduce debuginfo verbosity with
%global optflags %(echo %{optflags} | sed 's/-g /-g1 /')
Is that OK to do? I.e., does that not violate the guidelines?
and/or reduce parallelism during build (eg. make -j1)
I'm running with -j1 now, but it's taking forever. Using %make_build
uses up all the memory, though. Maybe I'll try with -j2 or -j3 next to
see if that speeds it up somewhat while not killing the machine.
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) |
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London