2011/9/30 Alexander Neundorf <a.neundorf-w...@gmx.net>: >> Summary: >> >> build dry rebuild >> ninja 1m15.8 0m0.1 0m07.3 >> make 1m19.4 0m1.4 0m07.9 >> auto 3m19.9 0m2.1 0m13.0 >> >> So only the dry run shows a huge speedup (10-20 times faster) > > Not to question your numbers, but shouldn't the difference of the dryrun > (1.3s) also be present in the rebuild ? > I mean, this should be the time ninja is faster in checking whether any file > changed, and in the rebuild case it has to do that too, and additionally build > one file ? > > How often did you measure this, just once or multiple times ?
I was about to comment about this too. If you do test ninja first on a pristine source tree and then make then make will certainly take advantage of the VFS caching almost all source file access. May be it would necessary to untar the source (in different temp dir ) before each test sets. but may you already did this. Or may be I should just try myself :-] -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
