164 lines
12 KiB
HTML
164 lines
12 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
|
||
|
|
<title>Application server tuning parameters</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h4><a name="prftuneappsvr"></a>Application server tuning parameters</h4>
|
||
|
|
|
||
|
|
<p>You can tune application server settings to control how an application server provides services for running applications and their components. Each application server instance contains interrelated components, called a queuing network, that must be properly tuned to support the specific needs of your e-business application. The queuing network helps the system achieve maximum throughput and maintain the overall stability of the system. For more information about the queuing network, see <a href="prftuneqnet.htm">Queuing network</a>.</p>
|
||
|
|
|
||
|
|
<p>You can tune the following application server settings:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li><a href="#webcont">Web container</a></li>
|
||
|
|
<li><a href="#sess">Session management</a></li>
|
||
|
|
<li><a href="#data">Data sources</a></li>
|
||
|
|
<li><a href="#pro">Process Priority</a></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p><strong><a name="webcont"></a>Web container</strong></p>
|
||
|
|
|
||
|
|
<p>Each application server includes a Web container. The application server routes servlet requests along a transport queue between the Web server plug-in and the Web container. Default Web container properties are set for simple Web applications. However, these values might not be appropriate for more complex Web applications. You can adjust these parameters to tune the Web container based on the specific needs of your environment:</p>
|
||
|
|
<ul>
|
||
|
|
<li><strong>Thread pool Maximum size</strong>
|
||
|
|
<ul>
|
||
|
|
<li>Description: This value limits the number of requests that your application server can process concurrently. For more information, see <a href="help/uejb_rthrd.html">Thread pool settings</a>. <img src="help.gif" width="18" height="15" align="absbottom" alt="Go to Help documentation">
|
||
|
|
<p><strong>Note:</strong> The information on the settings page applies to all thread pools in WebSphere Application Server - Express.</p></li>
|
||
|
|
<li>How to view or set:
|
||
|
|
<ol>
|
||
|
|
<li><a href="acstart.htm">Start the administrative console</a>.</li>
|
||
|
|
<li>In the topology tree, expand <strong>Servers</strong> and click <strong>Application Servers</strong>.</li>
|
||
|
|
<li>Click the name of the application server that you want to configure.</li>
|
||
|
|
<li>Click <strong>Web Container</strong>.</li>
|
||
|
|
<li>On the <strong>Web Container</strong> page, click <strong>Thread Pool</strong>.</li>
|
||
|
|
<li>Specify a value for the <strong>Maximum size</strong> field.</li>
|
||
|
|
<li>Click <strong>Apply</strong> or <strong>OK</strong>.</li>
|
||
|
|
<li><a href="acsave.htm">Save the configuration</a>.</li>
|
||
|
|
<li>Stop and restart the application server.</li>
|
||
|
|
</ol></li>
|
||
|
|
<li>Default value: 50</li>
|
||
|
|
<li>Recommended value: This value should be set to handle the peak load on your application server. It is recommended that you specify a maximum size less than or equal to the number of threads processing requests in your HTTP server. A value in the range 25-50 is generally a good starting point.</li>
|
||
|
|
</ul></li>
|
||
|
|
<li><strong>Growable thread pool</strong>
|
||
|
|
<ul>
|
||
|
|
<li>Description: This setting specifies whether the number of threads can increase beyond the maximum size configured for the thread pool. For more information, see <a href="help/uejb_rthrd.html">Thread pool settings</a>. <img src="help.gif" width="18" height="15" align="absbottom" alt="Go to Help documentation"></li>
|
||
|
|
<li>How to view or set:
|
||
|
|
<ol>
|
||
|
|
<li><a href="acstart.htm">Start the administrative console</a>.</li>
|
||
|
|
<li>In the topology tree, expand <strong>Servers</strong> and click <strong>Application Servers</strong>.</li>
|
||
|
|
<li>Click the name of the application server that you want to configure.</li>
|
||
|
|
<li>Click <strong>Web Container</strong>.</li>
|
||
|
|
<li>On the <strong>Web Container</strong> page, click <strong>Thread Pool</strong>.</li>
|
||
|
|
<li>Select <strong>Allow thread allocation beyond maximum thread size</strong>.</li>
|
||
|
|
<li>Click <strong>Apply</strong> or <strong>OK</strong>.</li>
|
||
|
|
<li><a href="acsave.htm">Save the configuration</a>.</li>
|
||
|
|
<li>Stop and restart the application server.</li>
|
||
|
|
</ol></li>
|
||
|
|
<li>Default value: Disabled</li>
|
||
|
|
<li>Recommended value: It is recommended that you do not enable this property if you are confident the thread pool maximum size is large enough to adequately process the peak load on your application server. If you want to allow the thread pool to exceed the configured maximum pool size, enable this property. This setting is beneficial if the application server receives an unexpected increase in requests or if the maximum pool size is set too low. In this scenario, additional threads are created to handle the increased number of requests. These connections are destroyed when the number of requests returns to its typical level. However, enabling the growable thread pool setting might cause a large number of threads to be created, and can have a negative impact on system storage and performance.</li>
|
||
|
|
</ul></li>
|
||
|
|
<p>You can also tune several custom parameters for HTTP transports in the Web container. For more information, see <a href="acshttpcp.htm">Set custom properties for an HTTP transport</a>.</p>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p><strong><a name="sess"></a>Session management</strong></p>
|
||
|
|
|
||
|
|
<p>The installed default settings for session management are configured for optimal performance. For more information, see <a href="../program/sestune.htm">Tune session management</a> in <em>Application development</em> and <a href="help/uprs_rtuning_parameters.html">Tuning parameter settings</a>. <img src="help.gif" width="18" height="15" align="absbottom" alt="Go to Help documentation"></p>
|
||
|
|
|
||
|
|
<p><strong><a name="data"></a>Data sources</strong></p>
|
||
|
|
|
||
|
|
<p>Applications uses data sources to access databases. The following data source settings can affect performance:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li><strong>Connection pooling</strong> For moreinformation about connection pooling, see <a href="../program/datapool.htm">Connection pooling</a> in <em>Application Development</em> and <a href="help/udat_conpoolset.html">Connection pool settings</a>. <img src="help.gif" width="18" height="15" align="absbottom" alt="Go to Help documentation">
|
||
|
|
<ul>
|
||
|
|
<li>Maximum connection pool
|
||
|
|
<ul>
|
||
|
|
<li>Description: This value specifies the maximum number of managed connections for a pool.</li>
|
||
|
|
<li>How to view or set:
|
||
|
|
<ol>
|
||
|
|
<li><a href="acstart.htm">Start the administrative console</a>.</li>
|
||
|
|
<li>In the topology tree, expand <strong>Resources</strong> and click <strong>JDBC Providers</strong>.</li>
|
||
|
|
<li>Click the name of the provider for the data source that you want to configure.</li>
|
||
|
|
<li>Click <strong>Data Sources</strong>.</li>
|
||
|
|
<li>Click the name of the data source that you want to configure.</li>
|
||
|
|
<li>Click <strong>Connection Pool</strong>.</li>
|
||
|
|
<li>Specify a value in the <strong>Max Connections</strong> field.</li>
|
||
|
|
<li>Click <strong>Apply</strong> or <strong>OK</strong>.</li>
|
||
|
|
<li><a href="acsave.htm">Save the configuration</a>.</li>
|
||
|
|
<li>Stop and restart the application server.</li>
|
||
|
|
</ol></li>
|
||
|
|
<li>Default value: 10</li>
|
||
|
|
<li>Recommended value: Set the value for the connection pool lower than the value for the <a href="#webcont"><strong>Max Connections</strong> option in the Web container</a>. If the pool is larger than necessary, it might waste memory and other system resources. A setting of 10-25 is suitable for many applications. For additional about connection pool size, see <a href="prftuneqnet.htm">Queuing network</a>.</li>
|
||
|
|
</ul></li>
|
||
|
|
<li>Minimum connection pool
|
||
|
|
<ul>
|
||
|
|
<li>Description: This value specifies the minimum number of managed connections for a pool.</li>
|
||
|
|
<li>How to view or set:
|
||
|
|
<ol>
|
||
|
|
<li><a href="acstart.htm">Start the administrative console</a>.</li>
|
||
|
|
<li>In the topology tree, expand <strong>Resources</strong> and click <strong>JDBC Providers</strong>.</li>
|
||
|
|
<li>Click the name of the provider for the data source that you want to configure.</li>
|
||
|
|
<li>Click <strong>Data Sources</strong>.</li>
|
||
|
|
<li>Click the name of the data source that you want to configure.</li>
|
||
|
|
<li>Click <strong>Connection Pool</strong>.</li>
|
||
|
|
<li>Specify a value in the <strong>Min Connections</strong> field.</li>
|
||
|
|
<li>Click <strong>Apply</strong> or <strong>OK</strong>.</li>
|
||
|
|
<li><a href="acsave.htm">Save the configuration</a>.</li>
|
||
|
|
<li>Stop and restart the application server.</li>
|
||
|
|
</ol></li>
|
||
|
|
<li>Default value: 1</li>
|
||
|
|
<li>Recommended value: Set the minimum pool size to handle the average load on the system.</li>
|
||
|
|
</ul></li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li><strong>Statement cache size</strong>
|
||
|
|
<ul>
|
||
|
|
<li>Description: WebSphere Application Server - Express provides a statement cache for each data source. This value represents the number of free prepared statements per connection in the connection pool. The statement cache stores query information for the data source. You can adjust to size of the statement cache to optimize performance. For more information, see <a href="help/udat_jdbcdatsordet.html#DataSource_statementCacheSize_displayName">Data source settings</a>. <img src="help.gif" width="18" height="15" align="absbottom" alt="Go to Help documentation"></li>
|
||
|
|
<li>How to view or set:
|
||
|
|
<ol>
|
||
|
|
<li><a href="acstart.htm">Start the administrative console</a>.</li>
|
||
|
|
<li>In the topology tree, expand <strong>Resources</strong> and click <strong>JDBC Providers</strong>.</li>
|
||
|
|
<li>Click the name of the provider for the data source that you want to configure.</li>
|
||
|
|
<li>Click <strong>Data Sources</strong>.</li>
|
||
|
|
<li>Click the name of the data source that you want to configure.</li>
|
||
|
|
<li>Specify a value in the <strong>Statement Cache Size</strong> field.</li>
|
||
|
|
<li>Click <strong>Apply</strong> or <strong>OK</strong>.</li>
|
||
|
|
<li><a href="acsave.htm">Save the configuration</a>.</li>
|
||
|
|
<li>Stop and restart the application server.</li>
|
||
|
|
</ol></li>
|
||
|
|
<li>Default value: 10</li>
|
||
|
|
<li>Recommended value: In most situations, it is recommended that you set this to the number of unique statements for each application that uses the datasource. Setting the cache size to this value avoids cache discards, and generally results in the best performance. However, if the cache is too large, it might cause performance problems as a result of increased cache management and increased use of system resources. If you have a large number of unique statements, a smaller number might be appropriate. For information about tuning the statement cache size, see <a href="http://www.ibm.com/servers/eserver/iseries/perfmgmt/pdf/stmntcache.pdf" target="_blank">Tuning the WebSphere Prepared Statement Cache</a>. <img src="www.gif" width="18" height="15" align="absbottom" alt="Link outside Information Center" border="0"></li>
|
||
|
|
</ul></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p><strong><a name="pro"></a>Process Priority</strong></p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li>Description: The priority setting establishes the application server job's run priority. The default process priority is 25. The application server does not override the default behavior of Java thread creation. Worker threads within the server are configured to run at 6 levels lower than the job's run priority. Therefore, by default, the priority of the worker threads is 31. For more information about this setting, see <a href="help/urun_rprocexec.html">Process execution settings</a>. <img src="help.gif" width="18" height="15" align="absbottom" alt="Go to Help documentation"></li>
|
||
|
|
<li>How to view or set:
|
||
|
|
<ol>
|
||
|
|
<li><a href="acstart.htm">Start the administrative console</a>.</li>
|
||
|
|
<li>In the topology tree, expand <strong>Servers</strong> and click <strong>Application servers</strong>.</li>
|
||
|
|
<li>Click the name of the application server that you want to configure.</li>
|
||
|
|
<li>Click <strong>Process Definition</strong>.</li>
|
||
|
|
<li>Click <strong>Process Execution</strong>.</li>
|
||
|
|
<li>On the <strong>Process Execution</strong> page, specify a value in the <strong>Process Priority</strong> field.</li>
|
||
|
|
<li>Click <strong>Apply</strong> or <strong>OK</strong>.</li>
|
||
|
|
<li><a href="acsave.htm">Save the configuration</a>.</li>
|
||
|
|
<li>Stop and restart the application server.</li>
|
||
|
|
</ol></li>
|
||
|
|
<li>Default value: 25</li>
|
||
|
|
<li>Recommended value: In most situations, the default value is acceptable. However, if other workloads are running at a higher priority (that is, with a lower priority number), you might need to adjust the application server's priority so that it can more easily access the necessary resources.</li>
|
||
|
|
</ul></li>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|