Developer mode, Buffering, Enhancing oraclejsp performance – Oracle Audio Technologies A86828-01 User Manual

Page 63

background image

OracleJSP Page Performance Tuning

Optimizing Apache JServ


Developer Mode

Another parameter that has a significant effect on performance is developer mode.
It is a useful feature for debugging during development, but it degrades
performance. The default value is true, so you will need to set it to false in the file as follows:

With developer mode set to true, OracleJSP and the servlet engine examines every
request to determine whether to reload or retranslate the page or application. With
developer mode off, only the first request is examined.

In a test using JDK 1.2 with 50 users, 128 MB heap, and the default TCP settings, the
performance gains with developer mode off were 14% in throughput, and 28% in
average response time.


If an OracleJSP page is not using any features that do not require resetting the buffer
(such as error pages, contextType settings, forwards, etc.), disabling the JSP page
buffer will improve performance. This is because memory will not be used in
creating the buffer, and the output can go directly to the browser. Use this page
directive to disable buffering:

<%@ page buffer=”none” %>

The default size of an OracleJSP page buffer is 8 KB.

Enhancing OracleJSP Performance

The Oracle JavaServer Pages Developer’s Guide and Reference provide detailed
information about Oracle JSP pages, implementation guidelines, configuration
issues, and performance tips, listed below:

Caching database connections

Since creating database connections is very expensive, it is more performant to use a
cache of connections. The OracleJSP application can then get a connection from the
pool of database connections and return it when it is finished.