SPEC Seal of Reviewal SPECjAppServer2001 Result
Copyright © 2002 Standard Performance Evaluation Corporation
Pramati Application Server 3.0 (Standard Edition) submission on DELL 2 CPU Xeon
57.38 BOPS@DualNode
1,101.60
US$/BOPS@DualNode
Submitter:
Pramati Technologies Ltd
SPEC license # 81 Test date:
Sep-2002
EJB Container Avail: Oct-2002
EJB Container JVM Avail: Aug-2002
Software
EJB Container
Supplier Domain Container
Emulator Container
Database
JDBC
Other Software
Hardware
J2EE Application Server
Database Server
Load Driver
Benchmark
Modifications
Configuration
Other Info
General Notes
Links
System Configuration Diagram

Full Disclosure Archive


Benchmark Settings
Orders Injection Rate: 34 Ramp Up Time: 600 seconds
# of Order Agents: 1 Ramp Down Time: 300 seconds
# of Manufacturing Agents: 1 Steady State Time: 1800 seconds
DB Load Injection Rate: 34 Trigger Time: 50 seconds
Total System Cost: US$63,211

Detailed Results
Order Transaction Mix Count Tx. Mix
New Order 30,213 50.10%
Change Order 12,034 19.95%
Order Status 12,114 20.09%
Customer Status 5,949 9.86%
Total # Order Transactions 60,310
Total # Manufacturing Transactions 42,976
Response Times Average Maximum 90th% Reqd
New Order 0.38 6.67 0.80 2.00
Change Order 0.46 7.52 1.20 2.00
Order Status 0.26 4.97 0.60 2.00
Customer Status 0.36 4.97 0.90 2.00
Manufacturing 2.97 11.12 5.00 5.00
Reproducibility Run (BOPS) 57.61

EJB Container
Name: Pramati Application Server v3.0 SP4 JVM Name: Sun J2SDK1.4.0_01
Vendor: Pramati Technologies Ltd JVM Vendor: Sun Microsystems
Available: Oct-2002 Available: Aug-2002
Instances: 1
Passed CTS: Dec-2001
Protocol: JRMP
Tuning Information
None
JVM Tuning Information
Garbage collection parameter : NewSize    = 128M
Garbage collection parameter : MaxNewSize = 128M

Maximum Java heap size = 750M

The bean pool sizes were tuned for the run. Details are available
in fdadeploypramati-j2ee-server.xml in the disclosure archive.

Supplier Domain Container
Name: Pramati Application Server v3.0 SP4 JVM Name: Sun J2SDK1.4.0_01
Vendor: Pramati Technologies Ltd JVM Vendor: Sun Microsystems
Available: Oct-2002 Available: Aug-2002
Tuning Information
None
JVM Tuning Information



Emulator Container
Name: Pramati Application Server v3.0 SP4 JVM Name: Sun J2SDK1.4.0_01
Vendor: Pramati Technologies JVM Vendor: Sun Microsystems
Available: Oct-2002 Available: Mar-2002
Tuning Information
Max worker threads : 400.

Keep-Alive is turned off.
JVM Tuning Information
Max heap size : 128M

Database
Name: Oracle9i Database Standard Edition for Windows 2000 9.0.1.1.1 (Release 1)
Vendor: Oracle
Available: Aug-2000
Tuning Information


JDBC
Name: oracle.jdbc.OracleDriver
Vendor: Oracle
Available: Aug-2000
Tuning Information
SPECj datasource :
Connection pool size : 40

Other Software
Name:
Vendor:
Available:
Tuning Information


J2EE Application Server (1 system)
Hardware Vendor: Dell Computer Corporation OS Vendor: Microsoft Corporation
Model Name: Dell PowerEdge 4600 OS Name: Windows 2000 Server
Processor: Intel Xeon Filesystem: NTFS
MHz: 2200 Disks: 1x18Gb 10K RPM Ultra-160
# of CPUs: 2 cores, 2 chips, 1 core/chip Network Interface: (2) 100BaseT Ethernet
Memory (MB): 1024 Other Hardware:
L1 Cache: # of Systems: 1
L2 Cache: 512KB H/W Available: Aug-2000
Other Cache: OS Available: Aug-2002
Notes / Tuning Information


Database Server (1 system)
Hardware Vendor: Dell Computer Corporation OS Vendor: Microsoft Corporation
Model Name: Dell PowerEdge 1400SC OS Name: Windows 2000 Server
Processor: Intel Pentium III Filesystem: NTFS
MHz: 1300 Disks: 3x18Gb 10K RPM U160
# of CPUs: 1 core, 1 chip, 1 core/chip Network Interface: 100BaseT Ethernet
Memory (MB): 1024 Other Hardware:
L1 Cache: # of Systems: 1
L2 Cache: 512KB H/W Available: Dec-2001
Other Cache: OS Available: Nov-2001
Notes / Tuning Information


Load Driver (1 system)
Hardware Vendor: Dell Computer Corporation OS Vendor: Microsoft Corporation
Model Name: GX 150 OS Name: Windows 2000 WorkStation
Processor: Pentium IV Filesystem: NTFS
MHz: 1400 Disks: 1x9GB
# of CPUs: Network Interface: 10/100BaseT
Memory (MB): 256 Other Hardware:
L1 Cache: # of Systems: 1
L2 Cache: H/W Available: Feb-2001
Other Cache: OS Available: Jan-2001
Notes / Tuning Information
Driver JVM used: Sun J2SDK1.4.0_01

Benchmark Modifications
Schema Modifications:
  The following index was added to the schema to improve query performance
  
  CREATE INDEX M_lo_idx on M_largeorder(lo_id)
Load Program Modifications:
  The load programs were not modified
Reference Bean Modifications:
  No changes were made to the reference beans

Benchmark Configuration Information
Persistence Mode Used:
  All beans were deployed using Container Managed Persistence (CMP)
Isolation Requirement Info:
  The database was configured with the default isolation-level of READ_COMMITED
  
  The following beans were deployed with an isolation level of 'READ_COMMITED'
  With this isolation-level, the appserver will load the entities at the beginning
  of the transaction and commit at the end of the transaction, if the entities have
  been modified during the course of the transaction
  
  RuleEnt
  CustomerEnt
  LargeOrderEnt
  SupplierEnt
  
  The following beans were deployed with an isolation level of 'OPTIMISTIC_REPEATABLE_READ'
  With this isolation-level, the appserver will load the entity once and cache it. At the
  end of the transaction, if the entity has changed a verified update (all fields) will occur.
  If successful, the cache is updated with the latest values. If the update was not successful
  the transaction is rolled back and cached entity removed. If the bean state has not changed,
  a verified select will ensure the entity has not changed in the database. If the verified
  select is not successful, the transaction is rolled back and cached entity is removed.
  
  DiscountEnt
  ItemEnt
  ComponentEnt
  AssemblyEnt
  BomEnt
  PartEnt
  SupplierCompEnt
  POEnt
  
  The following beans were deployed with the isolation level 'REPEATABLE_READ'
  With this isolation-level, the appserver will obtain a lock on the entity in
  the database (SELECT FOR UPDATE) at the begining of the transaction. If the entity
  has changed during the course of the transaction the changed values are commited to the database.
  
  SequenceEnt
  OrderLineEnt
  OrderCustomerEnt
  OrderEnt
  WorkOrderEnt
  InventoryEnt
  SComponentEnt
  POLineEnt
Durability Requirement Info:
  Software RAID Level 1 disk mirroring was used to ensure
  durability of the disk used for database logs.
Storage Requirement Info:
  Database data and log devices are created using reference scripts.
  The data device size and log device size are 18 GB each, which are
  sufficient for published transaction rate. Three disks were used
  1 for data and 2 for logs All the tables were created on a single disk.
  
  A 45 minute run at an injection rate of 34 increased storage use by
  0.3 GB. Given linear scaling, eight hours of run time would at that
  rate require 3.2 GB. The system was configured with 18GB of disk
  storage which is sufficient for the 8 hour run.
Argument Passing Semantics:
  Pramati Application Server uses pass-by-value semantics by default

Other Benchmark Information
  The xerces.jar file included in the SPECjAppServer2001 kit was added
  to the classpath and used. The version is not known.
  
  No software or hardware was used to influence network traffic.
  
  Load Balancing was not performed.

General Notes
The ords.err and plannedlines.err contain ConnectExceptions. Due to momentary
spikes in the network load the RMI runtime received some 'connection refused
exceptions'.


For questions about this result, please contact the submitter: Pramati Technologies Ltd
For other inquiries, please contact webmaster@spec.org

Benchmark run on Mon Sep 16 19:12:12 IST 2002 by SPECjAppServer2001 v1.12
Result submitted on Thu Sep 19 03:03:00 EDT 2002
Report generated by SPECjAppServer2001 Reporter v1.09

Copyright © 2002 Standard Performance Evaluation Corporation

First published at SPEC.org on 10-Oct-2002