Hardware |
Hardware Vendor |
Fujitsu Siemens Computers |
Vendor URL |
http://www.fujitsu-siemens.com |
Model |
PRIMERGY RX220, AMD Opteron(TM) 285 processor |
Processor |
AMD Opteron(TM) 285 processor, 2.60GHz, 2x1MB L2 |
MHz |
2600 |
# of Chips |
2 |
# of Cores |
4 |
# of Cores/Chip |
2 |
HW Threading Enabled? |
n/a |
Procs Avail to Java |
4 |
Memory (MB) |
16384 |
Memory Details |
8x2GB DDR-RAM PC2-3200R (CAS 3-3-3) |
Primary cache |
64KBI + 64KBD on chip, per core |
Secondary cache |
1MB(I+D) on chip, per core |
Other cache |
n/a |
Filesystem |
NTFS |
Disks |
1 x 80GB, Maxtor (SATA) |
Other hardware |
none |
|
Software |
Software Vendor |
BEA Systems, Inc |
Vendor URL |
http://www.bea.com |
JVM Version |
BEA JRockit(R) 5.0 P26.4.0 (build P26.4.0-10-62459-1.5.0_06-20060529-2101-win-x86_64) |
JVM Command Line |
start /AFFINITY %NODE_CPUs% /B java -Xms3700m -Xmx3700m -XXaggressive -XXthroughputCompaction -XXallocPrefetch -XXallocRedoPrefetch -XXcompressedRefs -XXlazyUnlocking -XXtlasize128k spec.jbb.JBBmain -propfile SPECjbb.props |
JVM Initial Heap Memory (MB) |
3700 |
JVM Maximum Heap Memory (MB) |
3700 |
JVM Address bits |
64 |
JVM CLASSPATH |
.\jbb.jar; .\check.jar;
|
JVM BOOTCLASSPATH |
C:\SPECjbb2005\JVM\P26.4.0\jre\bin\jrockit\jrockit.jar; C:\SPECjbb2005\JVM\P26.4.0\jre\bin\jrockit\managementapi.jar; C:\SPECjbb2005\JVM\P26.4.0\jre\lib\managementapi.jar; C:\SPECjbb2005\JVM\P26.4.0\jre\lib\rt.jar; C:\SPECjbb2005\JVM\P26.4.0\jre\lib\i18n.jar; C:\SPECjbb2005\JVM\P26.4.0\jre\lib\sunrsasign.jar; C:\SPECjbb2005\JVM\P26.4.0\jre\lib\jsse.jar; C:\SPECjbb2005\JVM\P26.4.0\jre\lib\jce.jar; C:\SPECjbb2005\JVM\P26.4.0\jre\lib\charsets.jar; C:\SPECjbb2005\JVM\P26.4.0\jre\classes |
OS Version |
Microsoft Windows Server 2003 Enterprise x64 Edition + SP1 (64-bit) |
Other software |
none |
|
Test Information |
Tested by |
Fujitsu Siemens Computers |
SPEC license # |
22 |
Test location |
Paderborn, Germany |
Test date |
Aug 4, 2006 |
H/w available |
Aug-2006 |
JVM available |
Jun-2006 |
OS available |
Mar-2005 |
Other s/w available |
n/a |
|
Tuning |
Operating system tunings- Using the local security settings console, "lock pages in memory" was enabled for the user running the benchmark.
- JVM instance 0 was bound to the CPUs 0,1 of node 0<\li>
- JVM instance 1 was bound to CPUs 2,3 of node 1<\li>
|
|