search for: 671804minor

...ay be possible but, again, it only speaks > about the relative sizes of LLVM/Cray's compiler. Ok, here are some hard numbers for empty builds: LLVM empty build: /usr/bin/time make -j16 4.32user 2.47system 0:03.21elapsed 211%CPU (0avgtext+0avgdata 13376maxresident)k 0inputs+0outputs (0major+671804minor)pagefaults 0swaps Cray empty build: /usr/bin/time make dynamic-developer -j16 2.88user 1.06system 0:04.94elapsed 79%CPU (0avgtext+0avgdata 64208maxresident)k 0inputs+0outputs (0major+184605minor)pagefaults 0swaps The Cray empty build includes some really horrendous shell script trickery known as...

Nico Weber <thakis at chromium.org> writes: > On Tue, Nov 1, 2011 at 3:09 PM, David A. Greene <greened at obbligato.org> wrote: >> Óscar Fuentes <ofv at wanadoo.es> writes: >> >>> Okay, we can get rid of recursive make. However, as pointed out >>> elsewhere, removing recursive make will not make a difference on the >>> LLVM build. What

On Tue, Nov 01, 2011 at 06:27:35PM -0500, David A. Greene wrote: > Here is actual data comparing an empty LLVM build done recursively (the > LLVM build) and non-recursively (the Cray build). > > See this? > > 0inputs+0outputs (0major+671804minor)pagefaults 0swaps > > vs. this? > > 0inputs+0outputs (0major+184605minor)pagefaults 0swaps > > That's I/O. Sorry to disappoint you, but no, this isn't I/O. You have just shown that a LLVM build touches more mmap'd pages. Joerg

greened at obbligato.org (David A. Greene) writes: > Ok, here are some hard numbers for empty builds: > > LLVM empty build: > /usr/bin/time make -j16 > 4.32user 2.47system 0:03.21elapsed 211%CPU (0avgtext+0avgdata 13376maxresident)k > 0inputs+0outputs (0major+671804minor)pagefaults 0swaps So your 16-way machine takes 2.5 times more than my 4-way cheap desktop... > Cray empty build: > /usr/bin/time make dynamic-developer -j16 > 2.88user 1.06system 0:04.94elapsed 79%CPU (0avgtext+0avgdata 64208maxresident)k > 0inputs+0outputs (0major+184605minor)pagefau...