Mark Peloquin wrote:
> The problem lies in the 2.6.0-test4 folder and the presence of some
> unwanted data from a stray benchmark run. Our scripting, not expecting
> stray data, ended up using the stray data as 2.6.0-test4 results, thus
> corrupting the any comparisons to 2.6.0-test4-vs-2.6.0-test4-mm3 as
> well as the history graphs. For the immediate time being, disregard
> 2.6.0-test4 results in the 2.6.0-test4-vs-2.6.0-test4-mm3. The
> 2.6.0-test4 comparisons vs any other kernel (mm2 for example) will
> contain the correct 2.6.0-test4 results. I've fixed the problem and am
> in the process of regenerating the corrected comparisons and history
> graphs.
>
> It takes a few hours to regenerate the history graphs, I'll post the
> corrected data asap.
The corrected comparisons and history graphs are now available.
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/
http://ltcperf.ncsa.uiuc.edu/data/2.6.0-test4-mm3/2.6.0-test4-vs-2.6.0-test4-mm3/
Besides specjbb/volanomark differences reported earlier, some other
possible points of interest are:
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/dbench.xfs.throughput.plot.16.png
mm1/2 had lagged bk's on this data point, but in mm3 it seems to have
got it back plus a little.
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/kernbench.elapsed.plot.2.png
2.6.0-test4 was notably slower here, but mm's/bk's have improved/fixed it.
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/specsdet.throughput.plot.1.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/specsdet.throughput.plot.4.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/specsdet.throughput.plot.16.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/specsdet.throughput.plot.64.png
Showing a little drop in throughput here.
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tbench.throughput.plot.1.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tbench.throughput.plot.4.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tbench.throughput.plot.16.png
There points are worse than test4/bk's.
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tbench.throughput.plot.64.png
However, strangely enough, this point is better.
Seeing numerous differing data points in tiobench for many/most files
systems.
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tiobench.ext2.Random_Write_avglat.plot.1.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tiobench.ext2.Random_Write_avglat.plot.16.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tiobench.ext2.Random_Write_avglat.plot.64.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tiobench.ext2.Sequential_Read_avglat.plot.16.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tiobench.ext2.Sequential_Read_avglat.plot.64.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tiobench.ext2.Sequential_Write_avglat.plot.1.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tiobench.ext2.Sequential_Write_avglat.plot.16.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tiobench.ext2.Sequential_Write_avglat.plot.64.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tiobench.ext2.Sequential_Write_cpu.plot.64.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tiobench.ext2.Sequential_Write_thru.plot.64.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tiobench.ext3.Sequential_Write_avglat.plot.16.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tiobench.ext3.Sequential_Write_cpu.plot.16.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tiobench.ext3.Sequential_Write_avglat.plot.64.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tiobench.ext3.Sequential_Write_cpu.plot.64.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tiobench.jfs.Sequential_Write_avglat.plot.16.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tiobench.jfs.Sequential_Write_cpu.plot.16.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tiobench.jfs.Sequential_Write_avglat.plot.64.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tiobench.jfs.Sequential_Write_cpu.plot.64.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tiobench.xfs.Sequential_Read_avglat.plot.16.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tiobench.xfs.Sequential_Write_avglat.plot.16.png
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/tiobench.xfs.Sequential_Write_avglat.plot.64.png
The common theme here seems to be sequential write trends have changed
somewhat in the mm line. Tell me if any of these differences are deemed
insignificant and I'll disregard reporting them in the future.
|