JDBC Type 4 Driver Performance Tuning Guide for Version 1.1

ManualsBrandsHP ManualsServerHP NonStop G-Series

Page 1 Hewlett-Packard Company — 529619-002 April 8, 2005

HP NonStop™ JDBC Type 4 Driver

Performance Tuning Guide for Version 1.1

April 8, 2005

Author: Ken Sell

1 Introduction

Java applications and application environments continue to play an important role in

software system development. Database access accounts for a significant portion of the

time and resources used by many Java programs. As database access grows, its impact on

the overall performance of an application grows as well. This document contains tips for

optimizing performance when using the HP NonStop JDBC Type 4 Driver, version 1.1.

2 Overview

The NonStop JDBC Type 4 Driver is one of several components that are used in

accessing an HP NonStop SQL/MX database. Although this document focuses on the

Type 4 driver component specifically, it also talks about other related components where

applicable.

Optimizing performance can have many meanings, including:

• CPU usage on the client system (PC, HP-UX, etc.)

• Memory usage on the client system

• CPU usage on the HP NonStop server system

• Memory usage on the server system

• Throughput (number of transactions per second)

• Response time (the time it takes for the client application to respond)

Furthermore, the meaning of performance can vary when the scalability of a system is

considered. When applicable, this document indicates any negative impact that a

performance improvement might have on the scalability of an application.

Summary of content (6 pages)

PAGE 1
HP NonStop™ JDBC Type 4 Driver Performance Tuning Guide for Version 1.1 April 8, 2005 Author: Ken Sell 1 Introduction Java applications and application environments continue to play an important role in software system development. Database access accounts for a significant portion of the time and resources used by many Java programs. As database access grows, its impact on the overall performance of an application grows as well.
PAGE 2
HP NonStop JDBC Type 4 Driver Performance Tuning Guide for Version 1.0 3 NonStop JDBC Type 4 Driver Tuning Tips 3.1 Configuration Tips • • • • • • • Use connection pooling either explicitly with your own implementation, the Type 4 driver connection pooling mechanism (the default is no connection pooling), or implicitly through a product that supports connection pooling, such as BEA Weblogic Server, IBM WebSphere, etc. Use the maxPoolSize and minPoolSize properties to tune the connection pool.
PAGE 3
HP NonStop JDBC Type 4 Driver Performance Tuning Guide for Version 1.0 • • • • • • • • Turn off autocommit when possible (the default is on). All transaction levels might operate faster with autocommit turned off, although using this setting requires you to code commits. Leave autocommit on for single statements.
PAGE 4
HP NonStop JDBC Type 4 Driver Performance Tuning Guide for Version 1.0 5 SQL/MX Tuning Tip • See the SQL/MX Query Guide. 6 Hardware considerations • Use the fastest Ethernet possible. The 100-megabit-per-second operation offered by the HP 3863 Fast Ethernet ServerNet adapter (FESA) on the NonStop system is recommended. 7 TCP/IP Configuration • Set the “DATAFORWARDCOUNT” and “DATAFORWARDTIMER” SLSA subsystem values to 1. For additional information, see the LAN Configuration and Management Manual.
PAGE 5
HP NonStop JDBC Type 4 Driver Performance Tuning Guide for Version 1.0 information about SQL/MX Connectivity Services (MXCS) CPU and memory usage. For more information, see the Measure User’s Guide. 8.1 Tool Usage Examples 8.1.1 HPjmeter Run a program (test.TestManyThreads), enabling output of performance information (-Xeprof). Note: the -Xeprof Java option is available on HP-UX systems. The –Xprof option is available with most other Java implementations and provides similar profiling data.
PAGE 6
HP NonStop JDBC Type 4 Driver Performance Tuning Guide for Version 1.0 Note that a large amount of time is spent in com.tandem.t4jdbc.SQLMXPreparedStatement.execiteQuery() (executing the query). This indicates a good place to look for optimization. For example, you might improve your query’s performance by using recommendations in the SQL/MX Query Guide.