Andre Poenitz wrote: > More data, mathed this time. > > 'Lumped' means a Mathed.C #include'ing everything else. > > Times are real/user/sys. > > Now Lumped > > Null build 2.6/1.4/0.9 1.6/1.3/0.3 > > Full rebuild 154/132/12 48/ 44/ 1 > > change MathParser.C 12/1.5/1 48/ 44/ 1 > > So lumping everything together buys more than 30% in the common case of > a Null and 60% for Full builds. The downside is when actually _working_ > on single files in mathed, where there's an increas of 300%.
We could introduce a mechanism to manually remove some files from the lumped files. Then one has the lumped files for all the untouched code and a handfull files which will be compiled separate. Any ideas for this 'mechanism'? > > Given that there are 74 active .C files in mathed one approach might be > to create smaller lumps of, say approx. 15 files each to get uniform > improvement. > > I'll try that next. > > Andre' > -- Peter Kümmel
