By PerfRec on Feb 17, 2011
Oracle's SPARC T3-1 server, running the application, together with Oracle's SPARC Enterprise M3000 server running the database, have achieved a record result of 5000 users, with 0.523 seconds of average transaction response time, for the online component of the "Day in the Life" JD Edwards EnterpriseOne benchmark.
The "Day in the Life" benchmark tests the Oracle JD Edwards EnterpriseOne applications, running Oracle Fusion Middleware WebLogic Server 11g R1, Oracle Fusion Middleware Web Tier Utilities 11g HTTP server and JD Edwards EnterpriseOne 9.0.1 in Oracle Solaris Containers, together with the Oracle Database 11g Release 2.
The SPARC T3-1 server is 25% faster and has better response time than the IBM P750 POWER7 system, when executing the JD Edwards EnterpriseOne 9.0.1 Day in the Life test, online component.
The SPARC T3-1 server had 25% better space/performance than the IBM P750 POWER7 server.
The SPARC T3-1 server is 5x faster than the x86-based IBM x3650 M2 server system, when executing the JD Edwards EnterpriseOne 9.0.1 Day in the Life test, online component.
The SPARC T3-1 server had 2.5x better space/performance than the x86-based IBM x3650 M2 server.
The SPARC T3-1 server consolidated the application/web tier of the JD Edwards EnterpriseOne 9.0.1 application using Oracle Solaris Containers. Containers provide flexibility, easier maintenance and better CPU utilization of the server leaving processing capacity for additional growth.
The SPARC Enterprise M3000 server provides enterprise class RAS features for customers deploying the Oracle 11g Release 2 database software.
To obtain this leading result, a number of Oracle advanced technology and features were used: Oracle Solaris 10, Oracle Solaris Containers, Oracle Java Hotspot Server VM, Oracle Fusion Middleware WebLogic Server 11g R1, Oracle Fusion Middleware Web Tier Utilities 11g, Oracle Database 11g Release 2, the SPARC T3 and the SPARC64 VII based servers.
JD Edwards EnterpriseOne DIL Online Component Performance Chart
|SPARC T3-1, 1x1.65 GHz SPARC T3||128||Solaris 10||5000||9.0.1||2U||0.523|
|\*IBM Power 750, 1x3.55 GHz POWER7||120||IBM i7.1||4000||9.0||4U||0.61|
|IBM Power 570, 4x4.2 GHz POWER6||128||IBM i6.1||2400||8.12||4U||1.129|
|IBM x3650M2, 2x2.93 GHz X5570||64||OVM||1000||9.0||2U||0.29|
\* from http://www-03.ibm.com/systems/i/advantages/oracle/, IBM used Websphere
128 GB memory
16 x 300 GB 10000 RPM SAS
1 x 1 GbE NIC
64 GB memory
1 x 1 GbE NIC
Oracle Database 11g Release 2
Oracle Fusion Middleware 11g WebLogic server 11g R1 version 10.3.2
Oracle Fusion Middleware Web Tier Utilities 11g
Oracle Solaris 10 9/10
Mercury LoadRunner 9.10 with Oracle DIL kit for JD Edwards EnterpriseOne 9.0 update 1
Oracle's JD Edwards EnterpriseOne is an integrated applications suite of Enterprise Resource Planning software.
- Oracle offers 70 JD Edwards EnterpriseOne application modules to support a diverse set of business operations.
- Oracle 's Day-In-Life (DIL) kit is a suite of scripts that exercises most common transactions of J.D. Edwards EnterpriseOne applications including business processes such as payroll, sales order, purchase order, work order, and other manufacturing processes, such as ship confirmation. These are labeled by industry acronyms such as SCM, CRM, HCM, SRM and FMS.
- Oracle's DIL kit's scripts execute transactions typical of a mid-sized manufacturing company.
- The workload consists of online transactions. It does not include the batch processing job components.
- LoadRunner is used to run the workload and collect the users' transactions response times against increasing numbers of users from 500 to 5000.
- Key metric used to evaluate performance is the transaction response time which is reported by LoadRunner.
Key Points and Best Practices
Two JD Edwards EnterpriseOne and two Oracle Fusion Middleware WebLogic Servers 11g R1 coupled with two Fusion Middleware 11g Web Tier HTTP Servers instances on the SPARC T3-1 server were hosted in four separate Oracle Solaris Containers to demonstrate consolidation of multiple application and web servers.
Each Oracle Solaris container was bound to a separate processor set with 40 virtual processors allocated to each EnterpriseOne Server, 16 virtual processors allocated to each WebServer container and 16 to the default set. This was done to improve performance by using the physical memory closest to the processors, thereby, reducing memory access latency and reducing processor cross calls. The default processor set was used for network and disk interrupt handling.
The applications were executed in the FX scheduling class to improve performance by reducing the frequency of context switches.
A WebLogic Vertical cluster was configured on each WebServer container with seven managed instances each to load balance users' requests and to provide the infrastructure that enables scaling to high number of users with ease of deployment and high availability.
The database server was run in an Oracle Solaris Container hosted on the Oracle's SPARC Enterprise M3000 server.
- JD Edwards EnterpriseOne
- Dynamic SGA Tuning of Oracle Database on Oracle Solaris with DISM (pdf)
- Deploying Oracle Database on the Oracle Solaris Platform – An Introduction (pdf)
- Best Practices Guide for Deploying Oracle WebLogic Suite on Sun Systems (pdf)
- Deploying Oracle Database on Oracle Sun SPARC Enterprise M-series Systems (pdf)
- Virtualization Options for Oracle Database Deployments on Sun SPARC Enterprise T-series Systems (pdf)
Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Results as of 2/16/2011.