|
Hardware |
|---|
| Hardware Vendor |
Hitachi, Ltd. |
| Vendor URL |
http://www.hitachi.com/ |
| Model |
Hitachi Compute Blade 2000 GVAX55A2 Server Blade (3.46GHz Xeon X5690) |
| Processor |
Intel Xeon processor X5690 (Intel Turbo Boost Technology up to 3.73 GHz) |
| MHz |
3467 |
| # of Chips |
2 |
| # of Cores |
12 |
| # of Cores/Chip |
6 |
| HW Threading Enabled? |
Yes |
| Procs Avail to Java |
24 |
| Memory (MB) |
49152 |
| Memory Details |
6 x 8 GB 2Rx4 PC3-10600R-9, ECC |
| Primary cache |
32KB(I) + 32KB(D) on chip per core |
| Secondary cache |
256KB(I+D) on chip per core |
| Other cache |
12 MB(I+D) on chip per chip |
| Filesystem |
NTFS |
| Disks |
2 x 146 GB 10000 rpm Fibre Channel RAID1 configuration |
| Other hardware |
Hitachi Compute Blade 2000 Chassis, Hitachi 8Gb 2-port FC adapter, AMS500 (Disk Array system) |
|
|
Software |
|---|
| Software Vendor |
IBM Corporation |
| Vendor URL |
http://www.ibm.com |
| JVM Version |
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows Server 2008 amd64-64 jvmwa6460sr7-20100219_54049 (JIT enabled, AOT enabled) |
| JVM Command Line |
start /HIGH /AFFINITY [F,70,700,F000,70000,700000] java -Xaggressive -Xcompressedrefs -Xgcpolicy:gencon -Xmn1400m -Xms1875m -Xmx1875m -XlockReservation -Xnoloa -XtlhPrefetch -Xlp |
| JVM Initial Heap Memory (MB) |
1875 |
| JVM Maximum Heap Memory (MB) |
1875 |
| JVM Address bits |
64 |
| JVM CLASSPATH |
.\jbb.jar;
.\check.jar;
|
| JVM BOOTCLASSPATH |
C:\Program Files\IBM\WebSphere\AppServer\java\jre\bin\compressedrefs\jclSC160\vm.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\annotation.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\beans.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\java.util.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\jndi.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\logging.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\security.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\sql.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmorb.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmorbapi.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmcfw.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\rt.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\charsets.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\resources.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmpkcs.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmcertpathfw.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmjgssfw.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmjssefw.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmsaslfw.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmjcefw.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmjgssprovider.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmjsseprovider2.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmcertpathprovider.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmxmlcrypto.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\management-agent.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\xml.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\jlm.jar;
C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\javascript.jar |
| OS Version |
Microsoft Windows Server 2008 R2 Enterprise |
| Other software |
IBM WebSphere Application Server V7.0 for Windows on x86-64 bit |
|
|
Test Information |
|---|
| Tested by |
Hitachi, Ltd. |
| SPEC license # |
35 |
| Test location |
JAPAN |
| Test date |
May 31, 2011 |
| H/w available |
Feb-2011 |
| JVM available |
Feb-2010 |
| OS available |
Mar-2011 |
| Other s/w available |
|
|
|
Tuning |
|---|
- Turned off "Hardware Prefetch" in BIOS.
- Turned off "Adjacent Cache Line Prefetch" in BIOS.
- Turned off "L1 Data Prefetcher" in BIOS.
- Turned off "Data Reuse Optimization" in BIOS.
- Each JVM instance was affinitized to 2 cores of a socket.
- Using the local security settings console, "lock pages in memory" was enabled for the user running the benchmark.
|
|
