SPECjAppServer®2004 Result Copyright © 2004 Standard Performance Evaluation Corporation |
Sun Java (TM) Systems Application Server 9.0 Platform Edition with Postgres 8.2 |
|
Submitter: Sun Microsystems Inc. |
SPEC license # 6 | Test date: Jun-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 6.0 32-bit | ||||||
---|---|---|---|---|---|---|
|
PostgreSQL JDBC TYPE IV 8.2 | ||||||
---|---|---|---|---|---|---|
|
PostgreSQL 8.2.4 | ||||||
---|---|---|---|---|---|---|
|
J2EE Application Servers | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||
|
Emulator SW Config | ||||||||
---|---|---|---|---|---|---|---|---|
|
||||||||
|
Database SW Config | ||||||
---|---|---|---|---|---|---|
|
||||||
|
Driver SW Config | ||||||
---|---|---|---|---|---|---|
|
||||||
|
J2EE AppServer HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Database Server HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Load Driver HW Primary (Emulator) (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Load Satellite HW (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Benchmark Modifications |
---|
Schema Modifications:
Scripts to create the DB are included in the FDA. fill factor was modified on tables Added TABLE TXN_LOG_TABLE to support JMS transaction logging to database Added primary keys to tables |
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) were used for the database files and logs maintained on the Sun StorageTek 2540 Array. The caches in the Array are battery backed (72 hours) 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 85 minute run for this submission required less than 4GB of database storage. This extrapolates to less than 70GB for a 24 hour period. The Sun StorageTek 2540 Array drive capacity is 876GB 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 X4200 M2 (2x2220 SE ,2X73GB) A87-KPZ22H8GCBA 3 Sun Solaris 10 RTU 3 Sun SunSpectrum Upgrade: 3YGOLD, 24x7 W9D-A65-24-3G 3 Sun Sun Fire T2000, 1x1.2 GHz, 16 GB mem T20Z108B-16GA2G 1 Sun 4 Gb Dual FC PCI-X Host Bus Adapter SG-XPCI2FC-QF4 1 Sun SunSpectrum Upgrade: 3YGOLD, 24x7 W9D-T2000-8-24-3G 1 Sun StorageTek 2540, 12 x 146GB, 12*RAID XTA2540R01A2E1752 1 Sun SunSpectum Upgrade: 3Y GOLD, 24x7 W9D-ST2540-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 PostgreSQL PostgreSQL 8.2 Database EnterpriseDB PostgreSQL support (premium) 3 |
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 Postgres JDBC driver is a Type 4 JDBC driver Recoverable 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 transaction log records are written to the database in a single transaction. Database checkpoints during the Measurement Interval were done every 300 secs as per checkpoint=300 in the postgresql.conf |
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 07-Jul-2007