Hello,
These results represent running the following benchmarks on a large PPC64
machine (8-way with 64GB of RAM). To make the table somewhat less wide,
the following convention has been adopted:
***THIS IS DIFFERENT THAN BEFORE***
1) == 2.6.12-rc1
2) == 2.6.12-rc1 + current CKRM core patches + CONFIG_CKRM=n
3) == 2.6.12-rc1 + current CKRM core patches + CONFIG_CKRM=y
4) == 2.6.12-rc1 + current CKRM core patches + CONFIG_CKRM=y + 100
classes
5) == 2.6.12-rc1 + current CKRM core & memrc patches + CONFIG_CKRM=n
6) == 2.6.12-rc1 + current CKRM core & memrc patches + CONFIG_CKRM=y
7) == 2.6.12-rc1 + current CKRM core & memrc patches + CONFIG_CKRM=y +
100 classes
As before, instead of posting raw numbers, I have provide only the
summary percentage change per each run.
kernbench -- 32 threads, 20 iterations
percentage of elapsed time relative to mainline
----------------------------------------------------------------------
1) 100.00
2) 100.11
3) 100.07
4) 100.00
5) 100.06
6) 100.50
7) 100.15
dbench -- 20 clients, 20 iterations
percentage of throughput relative to mainline
----------------------------------------------------------------------
1) 100.00
2) 98.18
3) 94.16
4) 102.53
5) 96.42
6) 97.55
7) 103.24
tbench -- 10 clients, 20 iterations
percentage of throughput relative to mainline
----------------------------------------------------------------------
1) 100.00
2) 100.07
3) 99.27
4) 99.80
5) 98.53
6) 99.10
7) 99.56
SPECjbb [1] -- starting 1 warehouse, by 1s, to 20 warehouses,
20 iterations
percentage of score relative to mainline
----------------------------------------------------------------------
1) 100.00
2) 100.02
3) 99.52
4) 100.06
5) 100.26
6) 100.03
7) 100.18
SDET [2] -- 20 iterations
percentage of throughput relative to mainline
# scripts: 1 4 16 64 128
----------------------------------------------------------------------
1) 100.00 100.00 100.00 100.00 100.00
2) 99.19 99.58 99.87 101.54 97.82
3) 99.09 100.68 99.64 99.00 90.38
4) 101.26 100.47 100.74 100.51 89.51
5) 100.27 100.27 98.93 100.01 91.03
6) 100.26 99.33 98.41 99.83 94.48
7) 100.20 99.98 99.48 97.63 98.98
I have profiler output for all runs in all benchmarks, if anyone cares
to see what may have caused certain runs to behave as they did, I can do
a diffprofile and mail the results.
Thanks,
Nish
[1] Disclaimer:
SPEC(tm) and the benchmark name SPECjbb(tm) are registered trademarks
of the Standard Performance Evaluation Corporation. The benchmarking was
conducted for research purposes only and were non-compliant with the
following deviations from the rules:
1. It was run on hardware that does not meet the SPEC
availability-to-the public criteria. The machine was an
engineering sample.
[2] DISCLAIMER: SPEC(tm) and the benchmark name SDET(tm) are registered
trademarks of the Standard Performance Evaluation Corporation. This
benchmarking was performed for research purposes only, and the run
results are non-compliant and not-comparable with any published results.
-------------------------------------------------------
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
_______________________________________________
ckrm-tech mailing list
https://lists.sourceforge.net/lists/listinfo/ckrm-tech
