|
| 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 group 1 was run there. An explicit processor set was created with all of chip 2's virtual CPUs assigned to it, and group 2 and the Controller were run in that processor set.
|
| 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 -Xmx192g -Xms192g -Xmn181g -XX:+UseParallelOldGC -XX:ParallelGCThreads=108 -XX:+UseLargePages -XX:LargePageSizeInBytes=2g -XX:+AlwaysPreTouch
|
| Tuning |
Each backend was run with critical threads priority, one backend, together with its associated transaction injector, 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
|
