> Of course, it's always better with actual benchmarks. > In normal cases, the dependency checking will be often twice > as fast. > > Ways worse in some pathological cases: > > make package in lang/php/5.2 > before: 3m06s > after: 1m06s > -> /3 > > make print-package-signature from the top-level: > before: 230m21s > after: 30m52s > -> /7 !!
this is very very useful to make sure dpb doesn't rebuild needlessly. > > make package in meta/gnome > before: 11m43s > after: 32s > -> /20 !! > > typical out-of-date run (300 packages) > before: 4m53s > after: 1m40s > -> /3 the make package speedup will boost packaging quickly :-) thanks very much for that! several observations 1) when you restart a errored out package, dpb takes about 10-15 secs (or usually more) to scan make depends, and then very quickly it goes through configure, make, make fake by observing the cookies. 2) make plist on huge packages like kde-l10n is slow. will the speedups benefit in both the above cases? i decided to hold off rebuilding until hackathon is finished :-) otherwise you never get caught up as dpb rebuilds after each cvs up. thanks a bunch
