From: Steven P. <sl...@au...> - 2003-08-22 20:30:49
|
Mark Peloquin wrote: > Been awhile since results where posted, therefore this is a little long. > > > Nightly Regression Summary for 2.6.0-test3 vs 2.6.0-test3-mm3 > > Benchmark Pass/Fail Improvements Regressions > Results Results Summary > --------------- --------- ------------ ----------- > ----------- ----------- ------- > dbench.ext2 P N N 2.6.0-test3 > 2.6.0-test3-mm3 report > dbench.ext3 P N Y 2.6.0-test3 > 2.6.0-test3-mm3 report The ext3 dbench regression is very significant for multi threaded 193 -> 118. Looks like this regression first showed up in mm1 and does not exist in any of the bk trees. http://ltcperf.ncsa.uiuc.edu/data/history-graphs/dbench.ext3.throughput.plot.16.png > > volanomark P N Y 2.6.0-test3 > 2.6.0-test3-mm3 report Volanomark is significant as well. 10% drop in mm tree. This one also appeared to show up in mm1 although it was a 14% drop then so mm3 actually looks a little better. There were build errors on mm2 run so I don't have that data at this time. Following link illustrates the drop in mm tree for volanomark. http://ltcperf.ncsa.uiuc.edu/data/history-graphs/volanomark.throughput.plot.1.png SpecJBB2000 for high warehouses also took a bit hit. Probably the same root cause as volanomark. Here is the history plot for the 19 warehouse run. http://ltcperf.ncsa.uiuc.edu/data/history-graphs/specjbb.results.avg.plot.19.png Huge spike in idle time. http://ltcperf.ncsa.uiuc.edu/data/history-graphs/specjbb.utilization.idle.avg.plot.19.png > > http://ltcperf.ncsa.uiuc.edu/data/2.6.0-test3-mm3/2.6.0-test3-vs-2.6.0-test3-mm3/ > Steve |