Guidelines for Configuring Virtual Partitions on Cellular Platforms

14
SAP SD 2-tier
0.99
0.91
0.93
1
0.99
0.92
0.96
0.86
0.88
0.9
0.92
0.94
0.96
0.98
1
1.02
1A(nPar) 4A,3B 4B,3C 4C,2A
configurations
normalized SAPs
SPECjbb
0.99
0.88
0.92
1
0.99
0.9
0.93
0.82
0.84
0.86
0.88
0.9
0.92
0.94
0.96
0.98
1
1.02
1A(nPar) 4A,3B 4B,3C 4C,2A
configurations
normalized bops
The results from the various experiments done as a part of this focused study are specific to
the small nPartition configuration (with two cells connected to the same crossbar), and also
workloads chosen to be run on them. Different workloads may have different levels of
sensitivity to resource localities. The impact on the workload performance can be even
higher in larger nPartition configurations (for example, with cells connected to different
crossbars) that are hosting virtual partitions configured to have non-optimal resource
localities.
III) Memory Granule Size and Base Versus Floating Memory
The configuration 1B was used to study the impacts of having different memory granule sizes
and also different amounts of base and floating memory in the virtual partition on these two
workloads. Having128MB memory granules resulted in an additional impact of about 1.5-
2% degradation for the workloads. The 4096MB memory granules did not seem to exhibit
any noticeable performance improvement when compared to 1024MB granules.