JVM Instances |
jvm_Ctr_1(1), jvm_Backend_1(4), jvm_TxInjector_1(4)
|
OS Image Description |
os_1
|
Tuning |
Chip 1's virtual CPUs were left in the default processor set, and groups 1 and 2 were run there. A processor set was created, and chip 2's virtual CPUs were assigned to it, and groups 3 and 4, and the Controller, were run there.
|
Notes |
None
|
Parts of Benchmark |
Controller
|
JVM Instance Description |
jvm_1
|
Command Line |
psrset -e 1 priocntl -e -c FX -m 60 -p 60 java -Xmx2048m -Xms2048m -Xmn1536m
|
Tuning |
The controller JVM was run with critical thread priority in processor set 1.
|
Notes |
None
|
Parts of Benchmark |
Backend
|
JVM Instance Description |
jvm_1
|
Command Line |
[ psrset -e 1 ] priocntl -e -c FX -m 60 -p 60 java -Xmx109g -Xms109g -Xmn101g -XX:+UseParallelOldGC -XX:ParallelGCThreads=16 -XX:+UseLargePages -XX:LargePageSizeInBytes=2m -XX:+AlwaysPreTouch -XX:-UseBiasedLocking
|
Tuning |
Each backend was run with critical threads priority, two backends with associated transaction injectors in each processor set.
|
Notes |
None
|
Parts of Benchmark |
TxInjector
|
JVM Instance Description |
jvm_1
|
Command Line |
[ psrset -e 1 ] priocntl -e -c FX -m 60 -p 60 java -Xmx2048m -Xms2048m -Xmn1536m
|
Tuning |
Each transaction injector was run with critical threads priority, in the same processor set as its associated backend.
|
Notes |
None
|