We are announcing the release of Sun Blade X6270 based on Intel Xeon X5500 series processors. The new Intel Xeon processor adapts to your application demands by automatically and intelligently adjusting server performance and energy usage according to your application needs and offers best-in-class virtualization.
In this blog, I summarize the performance of Oracle Weblogic Application Server 10.3 on Sun Blade X6270.
The workload is a moderately complex benchmark involving different components, including JMS, WebServices, and external systems such as database. The baseline application involves a mix of HTTP and HTTPS protocol requests, the login action transaction are via secured protocol.
The application server configuration consists of a Sun Blade X6270 having 2 x Intel Xeon X5560 running at 2.8GHz clock speed and 24GB of memory. The Solaris 10 10/08 Operating System is also installed on the server.
The Intel Xeon processor 5500 series provides Turbo mode and Hyper-Threading mode options in the BIOS setup. The Turbo mode enables automatically increasing processor frequency when the system has plenty head room for power consumption. The Hyper-Threading mode enables engaging hyper-threading when needed, so that each socket containing 4 cores can effectively scales 8 threads. The test results were gathered with both Turbo mode and Hyper-Threading mode enabled.
Four instances of Oracle Weblogic Server were installed on 4 Solaris zones, and configured and tuned optimally on Sun Blade x6270 platform. For the database, we did not want to run into the network/disk contention so the database is created in /tmp. For this purpose, we used a Sun Fire E6900 and a Sun SPARC Enterprise M5000. The intention was to eliminate the database configuration issues and to just measure the Application Server machine scalability. Performance tests were done for the following configuration:
Tuning Information
The following tuning has been done to get the best performance with Sun Blade x6270.
Weblogic Application Server Tuning
Following tuning is applied to the startWebLogic.sh script in your application domain.
Use the following option only if you are not running WebLogic Server instances in the Managed Server mode:
|
-Dweblogic.management.discover=false |
We recommend setting the SocketReaders to 2 on Sun Blade x6270 for better throughput based on our benchmarks.
|
-Dweblogic.SocketReaders=2 [ or -Dweblogic.DevPollSocketReaders=2 ] |
Following tuning is applied to the config.xml in your application domain.
|
Tuning Parameter |
Value |
|
NativeIOEnabled |
TRUE |
|
JDBC Connection Pool: InitialCapacity and Max Capacity |
150 |
|
Prepared Statement Cache |
300 |
|
HTTP Logging |
Disabled |
|
AcceptBacklog |
500 |
|
Execute Queue |
<execute-queue> <name>default</name> <thread-count>60</thread-count> </execute-queue> |
For more information on performance tuning, see the Oracle WebLogic Server Performance and Tuning Guide (http://edocs.bea.com/wls/docs100/perform/).
Sun Java 6.0 Update 6 (1.6.0_06) Tuning
The WebLogic Server 10.3 supports Sun Java 1.6 and can take advantage of some of the performance improvements that have been made into this release. The following is the complete list of options that we used for our benchmark.
|
-Xms3000M
-Xmx3000M -Xmn800m -Xss128k -XX:+UseParallelGC -XX:+AggressiveHeap |
Network Tuning
For Solaris x86 Operating Systems, tuning parameters we used are as follows:
|
ndd -set /dev/tcp tcp_conn_req_max_q 16384 ndd -set /dev/tcp tcp_conn_req_max_q0 16384 ndd -set /dev/tcp tcp_xmit_hiwat 131072 ndd -set /dev/tcp tcp_recv_hiwat 131072 ndd -set /dev/tcp tcp_naglim_def 1 |
Conclusion
The Oracle WebLogic Server 10.3 on Sun Blade x6270 shows excellent scalability and performance. The application that was benchmarked represents a complex use-case with moderate to heavy database usage. The results shows 2.6 x transaction/sec improvements over Sun Blade x6250 having 2 Quad-Core Intel Xeon L5430 running at 2.66GHz clock speed with 32GB of Memory.
