SPARC T5-2 Performance Running Oracle Fusion Middleware SOA

Oracle's SPARC T5-2 server running Oracle Fusion Middleware SOA Suite 11g on Oracle Solaris 11 demonstrated 2.1x to 2.4x throughput improvement with 2x concurrency over a similarly configured SPARC T4-2 server for Fusion Order Demo and Oracle Service Bus (OSB) benchmark workloads using 5 KB message size.

  • Oracle Fusion Middleware SOA was deployed on virtualized environments using Oracle VM for SPARC to demonstrate consolidation of multiple SOA services onto a single system.

  • The benchmark demonstrates SPARC hardware crypto performance within an OSB service using 100-byte element encrypted with AES and signed with RSA128.

Performance Landscape

OSB Tests
System ch/co/th OS  Concurrency 
T5/T4 Test
SPARC T5-2
SPARC T5-2 (db)
1/8/64
2/32/256
Oracle
Solaris 11
144 2.1x http_passthrough
96 2.4x dyn_transform
64 2.3x body encryption

ch/co/th – chips, cores, threads


BPEL Test
System ch/co/th OS Users T5/T4 Test
SPARC T5-2
SPARC T5-2 (db)
1.5/24/192
2/32/256
S11 400 2.2x Fusion order demo

ch/co/th – chips, cores, threads

Configuration Summary

Application Server:

SPARC T5-2
2 x SPARC T5 processors, 3.6 GHz
256 GB memory
2 x 300 GB internal disks
Oracle Solaris 11.1
Oracle WebLogic 10.3.6
Oracle SOA 11.1.1.6 (PS5)
Oracle OSB 11.1.1.6 (PS5)
Oracle JDK 7

Database Server:

SPARC T5-2
2 x SPARC T5 processors, 3.6 GHz
256 GB memory
2 x 300 GB internal disks
1 x Sun Storage 6180, 16 x 146 GB SAS disks
Oracle Solaris 11.1
Oracle Database 11g Release 2 (11.2.0.3)

Benchmark Description

Three tests were performed as part of the Oracle SOA Suite profiling:

HTTP Passthrough (http_passthrough)

The client sends a 5 KB message to a HTTP Web Services Description Language (WSDL)-based proxy service on an Oracle Service Bus server. The proxy routes (using route action) the message to the backend servlet in a WLS domain. Oracle Service Bus monitoring is enabled as the message goes through the bus. The proxy's operation selection algorithm is SOAP Action Header. This workload involves more networking load than any of the other Oracle Service Bus microbenchmarks described.

Dynamic Transformation (dyn_transformation)

In this benchmark the HTTP proxy receives a 5 KB XML document. The XML document has an Xquery resource name in one of its leaf nodes. The pipeline uses an Xpath to retrieve the Xquery resource name and executes transformation on the inbound XML. The majority of CPU is spent on XML processing.

Body Encryption (body_encryption)

This benchmark tests the crypto performance within an Oracle Service Bus service. The client sends a 5 KB message, within which a 100-byte element is encrypted, to the WSDL-based Oracle Service Bus proxy service over HTTP. The WSDL binding references an Oracle Web Services Manager policy. The business service is also WSDL-based. The element is encrypted with AES and signed with RSA128. The encrypted element is decrypted, and the message is routed to the backend service as a clear SOAP message.

See Also

Disclosure Statement

Copyright 2013, 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 26 March 2013.

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