SPEC Seal of Reviewal SPECjAppServer2001 Result
Copyright © 2002 Standard Performance Evaluation Corporation
Novell exteNd Application Server 5.1
64.11 BOPS@DualNode
389.83
US$/BOPS@DualNode
Submitter:
Novell, Inc
SPEC license # 31 Test date:
Nov-2003
EJB Container Avail: Dec-2003
EJB Container JVM Avail: Dec-2003
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: 37 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: 37 Trigger Time: 90 seconds
Total System Cost: US$24,993

Detailed Results
Order Transaction Mix Count Tx. Mix
New Order 33,425 49.94%
Change Order 13,601 20.32%
Order Status 13,369 19.98%
Customer Status 6,532 9.76%
Total # Order Transactions 66,927
Total # Manufacturing Transactions 48,478
Response Times Average Maximum 90th% Reqd
New Order 0.29 5.81 0.60 2.00
Change Order 0.23 2.94 0.40 2.00
Order Status 0.09 2.27 0.20 2.00
Customer Status 0.13 2.19 0.30 2.00
Manufacturing 2.14 9.42 3.25 5.00
Reproducibility Run (BOPS) 64.11

EJB Container
Name: exteNd Application Server 5.1 JVM Name: J2RE1.4.2_01
Vendor: Novell, Inc JVM Vendor: Novell, Inc.
Available: Dec-2003 Available: Dec-2003
Instances: 1
Passed CTS: Nov-2002
Protocol: RMI/IIOP
Tuning Information
keepalive=false, ORBThreadPoolMax=30
JVM Tuning Information
Server run with the following command:
silverserver +server +XX:MaxTenuringThreshold=3 +XX:SurvivorRatio=20 +Xmn100m +Xms400M +Xmx400M +DORBThreadPoolMax=30

Supplier Domain Container
Name: exteNd Application Server 5.1 JVM Name: J2RE1.4.2_01
Vendor: Novell, Inc JVM Vendor: Novell, Inc.
Available: Dec-2003 Available: Dec-2003
Tuning Information
http connection threads = 20
JVM Tuning Information
Server run with the following command:
silverserver +server +XX:MaxTenuringThreshold=3 +XX:SurvivorRatio=20 +Xmn100m +Xms400M +Xmx400M +DORBThreadPoolMax=30

Emulator Container
Name: exteNd Application Server 5.1 JVM Name: JRE1.4.2_01-b06
Vendor: Novell, Inc JVM Vendor: Novell, Inc.
Available: Jan-2004 Available: Feb-2003
Tuning Information
silverserver +server +Xms400M +Xmx400M
JVM Tuning Information
+Xms400M
+Xmx400M

Database
Name: MySQL 4.0.16
Vendor: MySQL AB
Available: Dec-2003
Tuning Information
innodb_thread_concurrency=1000
read_buffer_size=2M
innodb_log_group_home_dir=DBLOG:/INNODBLOG
innodb_data_home_dir=DBDATA:/DATA
innodb_data_file_path=ibdata1:2000M;ibdata2:1000M:autoextend
innodb_mirrored_log_groups=1
innodb_log_files_in_group=3
innodb_log_file_size=170M
innodb_log_buffer_size=8M
innodb_flush_log_at_trx_commit=1
innodb_log_archive=0
innodb_buffer_pool_size=512M
innodb_additional_mem_pool_size=20M
innodb_lock_wait_timeout=200
key_buffer=16M
max_allowed_packet=5M
myisam_sort_buffer_size=32M
sort_buffer_size=4M
table_cache=256
transaction-isolation=READ-COMMITTED
max-connections=64
default-character-set=latin1
language=english
bind-address=0.0.0.0
port=3306
datadir=sys:/mysql/data
skip-locking

JDBC
Name: Connector/J Version 3.0.9
Vendor: MySQL AB
Available: Oct-2003
Tuning Information
Connection Pools were created on the AppServer
using the following commands:
SilverCMD   AddCP : ECperfDataSource
-J -A dba  -W sql -l MYSQLV2 -j "jdbc:mysql://DATABASEHOST/specjdb" -m 12 -x 128 -t 0 -w 1

Other Software
Name:
Vendor:
Available:
Tuning Information


J2EE Application Server (1 system)
Hardware Vendor: Dell OS Vendor: Novell, Inc
Model Name: Dell OptiPlex GX270 OS Name: NetWare 6.5 SP1
Processor: Pentium 4 Filesystem: NSS
MHz: 2400 Disks: 40GB EIDE 7200RPM
# of CPUs: 1 core, 1 chip, 1 core/chip Network Interface: Integrated Intel Gigabit (10/100/1000)
Memory (MB): 1024 Other Hardware: NetWare default installation using J2EE platform pattern
L1 Cache: 12KB(I)+8KB(D) # of Systems: 1
L2 Cache: 512KB H/W Available: Oct-2003
Other Cache: OS Available: Dec-2003
Notes / Tuning Information


Database Server (1 system)
Hardware Vendor: Hewlett-Packard OS Vendor: Novell, Inc
Model Name: Proliant DL380 G3 OS Name: NetWare 6.5 SP1
Processor: Xeon Filesystem: NSS
MHz: 2400 Disks: 6x18.2Gb 15K RPM Ultra-320
# of CPUs: 2 cores, 2 chips, 1 core/chip Network Interface: (1)Compaq NC7781 PCi-X Gigabit 10/100/1000
Memory (MB): 2048 Other Hardware: 72 hour battery backed 64 MB disk write cache was used for RAID1 disk.
L1 Cache: 12KB(I)+8KB(D) # of Systems: 1
L2 Cache: 512KB H/W Available: Jan-2003
Other Cache: OS Available: Dec-2003
Notes / Tuning Information


Load Driver (1 system)
Hardware Vendor: Compaq OS Vendor: Microsoft
Model Name: Proliant 3000 OS Name: Windows 2000 Server SP4
Processor: Pentium II Filesystem: NTFS
MHz: 450 Disks: 1x9GB
# of CPUs: 2 cores, 2 chips, 1 core/chip Network Interface: Compaq NC3120 Ethernet Adapter (100 MBS)
Memory (MB): 2096 Other Hardware:
L1 Cache: 512KB(I)+512KB(D) # of Systems: 1
L2 Cache: H/W Available: Jan-1999
Other Cache: OS Available: Jun-2003
Notes / Tuning Information
Driver JDK: 1.4.2_01-b06

Benchmark Modifications
Schema Modifications:
  Rather than creating unique indexes on schema tables,
  we created primary keys that are equivalent (created on same columns)
  to improve performance.
  We created a primary key on M_largeorder.LO_ID.
Load Program Modifications:
  none
Reference Bean Modifications:
  No changes were made to the reference beans.

Benchmark Configuration Information
Persistence Mode Used:
  CMP mode was used for all beans
Isolation Requirement Info:
  Beans with a REPEATABLE_READ requirement were deployed using
  isolationlevel=TRANSACTION_SERIALIZABLE in the deployment plan.
  Pessimistic locking using SELECT FOR UPDATE type semantics are used to
  implement TRANSACTION_SERIALIZABLE.
  Beans with a READ_COMMITTED requirement were deployed using
  isolationlevel=TRANSACTION_READ_COMMITTED.
Durability Requirement Info:
  RAID1 disk was used to ensure durability for the database logs.
  72 hour battery backed disk write cache was used for RAID1 disk.
  RAID1 disk was created from two 18 GB disks.
Storage Requirement Info:
  After running for 45 minutes at txRate=37, 545 MB of disk
  space was used. Extrapolating to an 8 hour run would
  require 5.677 GB, which is easily handled by the 17 GB
  log file RAID 1 volume and 62 GB data file RAID 0 volume used.
Argument Passing Semantics:
  Novell exteNd Application Server uses pass by value semantics.

Other Benchmark Information
  xerces.jar from the jAppServer2001 kit was deployed with the application.

General Notes
The AUDIT BMP beans were modified to use 'select count(*)' style instead of
'select count (*)' queries (white space is removed after count) so that they
would work with MySQL, see AuditSourceCodeChange.jar


For questions about this result, please contact the submitter: Novell, Inc
For other inquiries, please contact webmaster@spec.org

Benchmark run on Fri Nov 14 12:14:41 EST 2003 by SPECjAppServer2001 v1.14
Result submitted on Wed Nov 26 03:03:00 EST 2003
Report generated by SPECjAppServer2001 Reporter v1.09

Copyright © 2002 Standard Performance Evaluation Corporation

First published at SPEC.org on 12-Dec-2003