SPECjAppServer®2004 Result Copyright © 2004 Standard Performance Evaluation Corporation |
Sun Java (TM) Systems Application Server 9.0 Platform Edition on SunFire X4100 Cluster with MySQL 5 |
|
Submitter: Sun Microsystems Inc. |
SPEC license # 6 | Test date: Apr-2007 |
SUT Configuration | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||
|
Benchmark Settings | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Detailed Results | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||
|
||||||||||||||||||||||||||
|
||||||||||||||||||||||||||
|
Sun Java (TM) Systems Application Server 9.0 Platform Edition Update Release 1 Patch 3 | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Jakarta Tomcat 5.5.16 | ||||
---|---|---|---|---|
|
Java (TM) 2 Platform Standard Edition Development Kit 5.0 Update 6 32-bit | ||||||
---|---|---|---|---|---|---|
|
Connector/J 5.0.5 | ||||||
---|---|---|---|---|---|---|
|
MySQL 5.0.27 64-bit | ||||||
---|---|---|---|---|---|---|
|
J2EE Application Servers | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||
|
Emulator SW Config | ||||||||
---|---|---|---|---|---|---|---|---|
|
||||||||
|
Database SW Config | ||||||
---|---|---|---|---|---|---|
|
||||||
|
Driver SW Config Primary | ||||||
---|---|---|---|---|---|---|
|
||||||
|
J2EE AppServer HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Database Server HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Load Driver HW (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Benchmark Modifications |
---|
Schema Modifications:
Scripts to create the DB are included in the FDA. Two indexes were created on the M_largeorder table: CREATE UNIQUE INDEX M_lo_idx ON M_largeorder (lo_id) CREATE UNIQUE INDEX M_OL_O_idx ON M_largeorder (lo_o_id, lo_ol_id) Added TABLE TXN_LOG_TABLE to support JMS transaction logging to database Created the primary indexes via the MySQL primary key syntax |
Load Program Modifications:
The load program was not modified |
Benchmark Configuration Information |
---|
Isolation Requirement Info:
BEAN SPEC_REQUIREMENT Deployment Corp.CustomerEnt Repeatable Read Sel-4-Upd Corp.CustomerInventoryEnt Repeatable Read Sel-4-Upd Mfg.InventoryEnt Repeatable Read Sel-4-Upd Mfg.WorkOrderEnt Repeatable Read Sel-4-Upd Orders.OrderEnt Repeatable Read Sel-4-Upd Orders.OrderLineEnt Repeatable Read Sel-4-Upd Supplier.POEnt Repeatable Read Sel-4-Upd Supplier.POLineEnt Repeatable Read Sel-4-Upd Supplier.SComponentEnt Repeatable Read Sel-4-Upd Util.SequenceEnt Repeatable Read Sel-4-Upd Mfg.AssemblyEnt Read Committed RC Mfg.BomEnt Read Committed RC Mfg.ComponentEnt Read Committed RC Mfg.LargeOrderEnt Read Committed RC Mfg.PartEnt Read Committed RC Orders.ItemEnt Read Committed RC Supplier.SupplierCompEnt Read Committed RC Supplier.SupplierEnt Read Committed RC The ItemEnt bean was cached for 20 minute intervals by setting is-read-only-bean=true and refresh-period-in-seconds=1200 in the sun-orders.xml deployment descriptor. Only the data inside the bean was cached. |
Durability Requirement Info:
To ensure database durability, RAID 1 (mirror disks) was used for the database files and logs maintained on the Sun StorageTek 3510 Array. Each application server has a pair of mirrored disks (using Sun Fire integrated raid controller utility) to provide durability for the JMS messages. |
Storage Requirement Info:
The 80 minute run for this submission required less than 6GB of database storage. This extrapolates to less than 108GB for a 24 hour period. The Sun StorageTek 3510 Array drive capacity is 438GB of available storage when configured for RAID 1. |
Argument Passing Semantics:
Sun Java Systems Application Server 9.0 Platform Edition uses pass-by-value semantics by default. |
Bill of Materials |
---|
Supplier Description Product # Qty -------- ---------------------------------------- ------------------ --- Sun Sun Fire X4100 (2x285,4x2GB,2X73GB) A64-EGB2-2H-8G-CB7 3 Sun Solaris 10 RTU 3 Sun SunSpectrum Upgrade: 3YGOLD, 24x7 W9D-A64-24-3G 3 Sun Sun Fire X4100 (2x285,4x2GB,2X73GB) A64-EGB2-2H-8G-CB7 1 Sun Solaris 10 RTU 1 Sun Single-Port PCI Ultra320 SCSI HBA SGXPCI1SCSILM320-Z 1 Sun SunSpectrum Upgrade: 3YGOLD, 24x7 W9D-A64-24-3G 1 Sun StorageTek 3510, 12 x 73GB, 1 RAID XTA3510R01A1R876 1 Sun SunSpectum Upgrade: 3Y GOLD, 24x7 W9D-SE3510-24-3G 1 Sun 17" Entry Color Monitor X7204A 1 Sun USB Keyboard 320-1271 1 Sun USB Mouse 320-2632 1 Sun Sun Java System Application Server Platform Edition 9.0 Sun Sun Java System Application Server SJSAS-PE9F-1PR 18 Platform Edition 9.0 Premium Support per CPU for 1 year MySQL MySQL Database 5.0 MySQL MySQL Network Gold Support 3 for 1 year |
Other Benchmark Information |
---|
The submission used round-robin DNS for load-balance of all HTTP network requests. The DNS server was hosted on one of the application servers. The submission used multiple endpoints to establish connections to the EJB tier using RMI/IIOP. This submission used the xerces implementation 2.6.2 provided with the Sun Java System Application Server 9.0 Platform Edition. The emulator used xerces implementation 2.7.1 provided with the Jakarta Tomcat 5.5.16 |
General Notes |
---|
The only errors in the driver log files were those that are normally generated by this benchmark. The MySQL Connector/J JDBC Driver is a type 4 driver. XA 2-phase transactions were used to coordinate the interaction between the database server and JMS server using Sun's Last Agent Logging Optimization; the 1PC database transactions and XA logs are written to the database in a single transaction. Database checkpoints during the Measurement Interval were done by using continuous (fuzzy) checkpoints, where MySQL database engine InnoDB flushes modified database pages from the buffer pool in small batches. |
For questions about this result, please contact the submitter: Sun Microsystems Inc. For other inquiries, please contact webmaster@spec.org
Copyright © 2004 Standard Performance Evaluation Corporation
First published at SPEC.org on 27-Apr-2007