SPECjbb2015 Report for jbb2015-20151223-00039 : 98227 max-jOPS ; 28810 critical-jOPS

Hardware hw_1
Name	FusionServer CH121 V3
Vendor	Huawei Technologies Co., Ltd
Vendor URL	http://www.huawei.com/
Available	Sep-2014
Model	FusionServer CH121 V3
Form Factor	Blade Node in Chassis
CPU Name	Intel Xeon E5-2699 v3
CPU Characteristics	18-Core, 2.30GHz (Turbo Boost Technology up to 3.60 GHz)
Number of Systems	1
Nodes Per System	1
Chips Per System	2
Cores Per System	36
Cores Per Chip	18
Threads Per System	72
Threads Per Core	2
Version	None
CPU Frequency (MHz)	2300
Primary Cache	32KB(I)+32KB(D) per core
Secondary Cache	256 KB (I+D) per core
Tertiary Cache	45MB (I+D) on chip per chip
Other Cache	None
Disk	1x 480GB SSD
File System	EXT4
Memory Amount (GB)	256
# and size of DIMM(s)	16 x 16GB
Memory Details	256 GB (16 x 16 GB 2Rx4 PC4-2133P-R)
# and type of Network Interface Cards (NICs)	4 x 1 Gbit NICs
Power Supply Quantity and Rating (W)	1 x 2000W
Other Hardware	None
Cabinet/Housing/Enclosure	None
Shared Description	None
Shared Comment	None
Notes	None
Other Hardware network_1
Name	None
Vendor	None
Vendor URL	None
Version	None
Available	None
Bitness	None
Notes	None

Operating System os_1
Name	Red Hat Enterprise Linux
Vendor	Red Hat
Vendor URL	http://www.redhat.com/
Version	Red Hat Enterprise Linux Server release 7.0 (Maipo)
Available	June-2014
Bitness	64
Notes	None
Java Virtual Machine jvm_1
Name	Oracle Java SE 8u66
Vendor	Oracle Corporation
Vendor URL	http://www.oracle.com
Version	Java HotSpot 64-Bit Server VM, version 1.8.0_66
Available	Oct-2015
Bitness	64
Notes	note
Other Software other_1
Name	None
Vendor	None
Vendor URL	None
Version	None
Available	None
Bitness	None
Notes	None

Hardware
OS Images	os_Image_1(1)
Hardware Description	hw_1
Number of Systems	1
SW Environment	non-virtual
Tuning	BIOS tuning Power Policy was set to Performance COD mode was configured Memory Patrol Scrub was set to Disabled
Notes	notes

OS Image os_Image_1
JVM Instances	jvm_Ctr_1(1), jvm_Backend_1(4), jvm_TxInjector_1(4)
OS Image Description	os_1
Tuning	SE Linux = Disabled
Notes	None
JVM Instance jvm_Ctr_1
Parts of Benchmark	Controller
JVM Instance Description	jvm_1
Command Line	-Xmn1536m -Xms2g -Xmx2g
Tuning	None
Notes	None
JVM Instance jvm_Backend_1
Parts of Benchmark	Backend
JVM Instance Description	jvm_1
Command Line	-showversion -server -XX:LargePageSizeInBytes=2m -XX:+AggressiveOpts -XX:-UseAdaptiveSizePolicy -XX:+AlwaysPreTouch -XX:-UseBiasedLocking -XX:+UseLargePages -XX:+UseParallelOldGC -Xms29g -Xmx29g -Xmn27g -XX:SurvivorRatio=28 -XX:TargetSurvivorRatio=95 -XX:ParallelGCThreads=18 -XX:MaxTenuringThreshold=15 -XX:+PrintTenuringDistribution -XX:+PrintGCDetails -XX:+PrintGCTimeStamps
Tuning	numactl was used to affinitize each Backend JVM to a single numa node, eg: numactl --cpunodebind=$node --localalloc
Notes	None
JVM Instance jvm_TxInjector_1
Parts of Benchmark	TxInjector
JVM Instance Description	jvm_1
Command Line	-showversion -Xmn1536m -Xms2g -Xmx2g
Tuning	numactl was used to affinitize each TxInjector JVM to a single numa node, eg: numactl --cpunodebind=$node --localalloc
Notes	None

max-jOPS = jOPS passed before the First Failure
Pass/Fail	Pass	Pass	Fail	Fail	Fail
jOPS	97182	98227	99272	100317	101362

critical-jOPS = Geomean ( jOPS @ 10000; 25000; 50000; 75000; 100000; SLAs )
Response time percentile is 99-th
SLA (us)	10000	25000	50000	75000	100000	Geomean
jOPS	20376	25601	28736	33787	39186	28810

Note

(Actual % in the Mix - Expected % in the Mix) must be within:

'Main Tx' limit of +/-5.0% for the requests whose expected % in the mix is >= 10.0%

'Minor Tx' limit of +/-1.0% for the requests whose expected % in the mix is < 10.0%

There were no non-critical failures in Response Time curve building

This section lists properties only set by user

Property Name	Default	Controller
specjbb.comm.connect.client.pool.size	256	192
specjbb.comm.connect.selector.runner.count	0	4
specjbb.comm.connect.timeouts.connect	60000	650000
specjbb.comm.connect.timeouts.read	60000	650000
specjbb.comm.connect.timeouts.write	60000	650000
specjbb.comm.connect.worker.pool.max	256	320
specjbb.customerDriver.threads	64	{=64, probe=96, saturate=96}
specjbb.forkjoin.workers	72	{Tier1=170, Tier2=60, Tier3=30}
specjbb.group.count	1	4
specjbb.mapreducer.pool.size	72	27
specjbb.txi.pergroup.count	1	1


Level: COMPLIANCE
Check	Agent	Result
Check properties on compliance	All	PASSED

High-bound (max attempted) is 104497 IR

High-bound (settled) is 98137 IR

SPECjbb2015 Version: [SPECjbb2015 1.00, June 24, 2015]

Huawei Technologies Co., Ltd FusionServer CH121 V3	98227 SPECjbb2015-MultiJVM max-jOPS 28810 SPECjbb2015-MultiJVM critical-jOPS
Tested by: Huawei Technologies Co., Ltd	Test Sponsor: Huawei Technologies Co., Ltd	Test location: Shenzhen, China	Test date: Dec 21, 2015
SPEC license #: 3175	Hardware Availability: Sep-2014	Software Availability: Oct-2015	Publication: Jan 21, 2016


SPECjbb2015-MultiJVM: Multiple JVMs/Single Host (# of groups: 4) Overall SUT Description SUT Description max-jOPS and critical-jOPS Details Number of probes Request Mix Accuracy Rate Of Non-Critical Failures Delay between performance status pings IR/PR Accuracy Topology SUT Configuration Properties Validation Details Link to Full Disclosure	Overall Throughput RT curve