SPARC T3-1 Shows Capabilities Running Online Auction Benchmark with Oracle Fusion Middleware

Oracle produced the best performance of the Fusion Middleware Online Auction workload using Oracle's SPARC T3-1 server for the application server and Oracle's Sun SPARC Enterprise M4000 server for the database server.

  • The J2EE WebLogic application achieved 19,000 concurrent users with 4 WebLogic instances running an online auction workload.

  • The SPARC T3-1 server using the J2EE WebLogic application server software on Oracle Solaris 10 showed near-linear scaling of 3.7x on 4 WebLogic instances.

  • The SPARC T3-1 server has proven its capability of balancing a large number of interactive user sessions distributed across multiple hardware threads with sub-second response time while leaving processing capacity for additional growth.

  • The database server, a Sun SPARC Enterprise M4000 server, scaled well with a large number of concurrent user sessions and utilized all the CPU resources fully to serve 19,000 users.

  • Oracle Fusion Middleware provides a family of complete, integrated, hot plugable and best-of-breed products known for enabling enterprise customers to create and run agile and intelligent business applications. The Oracle WebLogic Server's on-going, record-setting Java application server performance demonstrates why so many customers rely on Oracle Fusion Middleware as their foundation for innovation.

  • To obtain this leading result a number of Oracle technologies were used: Oracle Solaris 10, Oracle Java Hotspot VM, Oracle WebLogic 10.3.3, Oracle Database 11g Release 2, SPARC T3-1 server, and Sun SPARC Enterprise M4000 server.

Performance Landscape

Online Auction POC Oracle Fusion Middleware Benchmark Results

Application Server Database Server Users Ops/
sec\*
1 x SPARC T3-1
1 x 1.65 GHz SPARC T3
Oracle WebLogic 10.3.3 - 4 Instances
Oracle Solaris 10 9/10
1 x Sun SPARC Enterprise M4000
2 x 2.53 GHz, SPARC64 VII
Oracle 11g DB 11.2.0.1
Oracle Solaris 10 9/10
19000 4821
2 x Sun Blade X6270,
Oracle WebLogic 10.3.3
– 8 Instances with Coherence, EclipselinkJPA
Oracle Solaris 10 10/09
1 x Sun SPARC Enterprise M5000
4 x 2.53 GHz, SPARC64 VII
Oracle 11g DB 11.2.0.1.0
Oracle Solaris 10 10/09
16500 4600
1 x SPARC T3-1
1 x 1.65 GHz SPARC T3
Oracle WebLogic 10.3.3 – 1 Instance
Oracle Solaris 10 9/10
1 x Sun SPARC Enterprise M4000,
2 x 2.53GHz, SPARC64 VII
Oracle 11g DB 11.2.0.1
Oracle Solaris 10 9/10
5000 1302

\* Online Auction Workload (Obay) Ops/sec, bigger is better.

Configuration Summary

Application Server Configuration:

1 x SPARC T3-1 server
1 x 1.65 GHz SPARC T3 processor
64 GB memory
1 x 10GbE NIC
Oracle Solaris 10 9/10
Oracle WebLogic 10.3.3 Application Server - Standard Edition
Oracle Fusion Middleware, Obay/DB Loader.1
Oracle Java SE, JDK 6 Update 21
Faban Harness and driver 1.0

Database Server Configuration:

1 x Sun SPARC Enterprise M4000 server
2 x 2.53 GHz SPARC64 VII processors
128 GB memory
1 x 10GbE NIC, 1 x 1GbE NIC
1 x StorageTek 2540 HW RAID controller
2 x Sun Storage 2501 JBOD Arrays
Oracle Solaris 10 9/10
Oracle Database Enterprise Edition Release 11.2.0.1

Benchmark Description

This Fusion Middleware Online Auction workload is derived from an auction demonstration application originally developed by Oracle based on Ebay's online auction model. The workload includes functions such as adding new product for auction, submitting bids, user login/logout and admin account setup. It requires a J2EE application server and database. The benchmark metric is the number of total users (bidders/sellers) accessing the items database and executing a number of operations per second with an average response time below a second. The online auction workload demonstrates the performance benefits of using Oracle Fusion Middleware integrated with Oracle servers.

Key Points and Best Practices

  • TCP tunable tcp_time_wait_interval was reduced to 10000 to respond to a large number of concurrent connections.

  • TCP tunable tcp_conn_req_max_q and tcp_conn_req_max_q0 were increased to 65536.

  • Four Oracle WebLogic application server instances were hosted on a single SPARC T3-1.

  • The WebLogic application servers were executed in the FX scheduling class to reduce the Context Switches.

  • The JVM used was 64-bit with the Heap was increased to 6 GB.

  • WebLogic server made use of a performance pack enabled by LD_LIBRARY_PATH native to SPARC64.

  • The Oracle database logwriter was bound to a core on the Sun SPARC Enterprise M4000 server and ran under the RT class.

  • The Oracle database processes were bound round robin to processors and executed in the FX scheduling class to reduce the thread migration and, hence, improved performance.

See Also

Disclosure Statement

Copyright 2010, 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. Reported 9/20/2010.

Comments:

Post a Comment:
Comments are closed for this entry.
About

BestPerf is the source of Oracle performance expertise. In this blog, Oracle's Strategic Applications Engineering group explores Oracle's performance results and shares best practices learned from working on Enterprise-wide Applications.

Index Pages
Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today