73 lines
4.4 KiB
HTML
73 lines
4.4 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>Tune session management</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h4><a name="sestune"></a>Tune session management</h4>
|
||
|
|
|
||
|
|
<p>WebSphere Application Server - Express for iSeries session support has features for tuning session performance and operating characteristics. You configure these options in the WebSphere administrative console. The settings are listed by which page in the console that they appear.</p>
|
||
|
|
|
||
|
|
<p><strong>Session management</strong></p>
|
||
|
|
|
||
|
|
<p>The Session Management page of the console contains these settings that are related to performance tuning:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li><p><strong>Overflow</strong> and <strong>Maximum in-memory session count</strong>
|
||
|
|
<br>These settings specify the maximum number of sessions that are retained in memory, and whether or not to ever exceed that number. For more information, see <a href="sesmaxim.htm">Maximum in-memory session count</a>.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>Serialize session access</strong>
|
||
|
|
<br>Specifies that concurrent session access in a given server is not allowed.</p></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<!--<p><strong>Database Settings</strong></p>
|
||
|
|
|
||
|
|
<p>In the Session Management page, click <strong>Distributed Environment Settings</strong>, and then click <strong>Database</strong>. The Database Setting page contains the <strong>Multi row schema</strong> setting, which can be used to tune performance for database-persisted sessions. For more information, see <a href="sesmulti.htm">Multi row schema</a>.</p>-->
|
||
|
|
|
||
|
|
<!--<p><strong>Tuning parameters</strong></p>
|
||
|
|
|
||
|
|
<p>In the Session Management page of the administrative console, click <strong>Distributed Environment Settings</strong>, and then click <strong>Custom Tuning Parameters</strong>. The Tuning Parameters page contains these tuning levels:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li>Very high</li>
|
||
|
|
<li>High</li>
|
||
|
|
<li>Medium</li>
|
||
|
|
<li>Low</li>
|
||
|
|
<li>Custom settings</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p>The tuning levels are comprised of settings that pertain to these concepts:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li><p><strong>Write frequency</strong>
|
||
|
|
<br>Minimize database write operations. This option is only available for database persistence and memory-to-memory replication. For more information, see <a href="seswrtfr.htm">Write frequency</a>.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>Write contents</strong>
|
||
|
|
<br>Allow flexibility in determining what session data to write. This option is only available for database persistence and memory-to-memory replication. For more information, see <a href="seswrtcn.htm">Write contents</a>.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>Schedule sessions cleanup</strong>
|
||
|
|
<br>Minimize contention between session requests and invalidation of sessions by the Session Management facility. Minimize write operations to database for updates to last access time only. Database and Memory-to-Memory. For more information, see <a href="sesclean.htm">Schedule sessions cleanup</a>.</p></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p>You can select a pre-defined tuning level, or click <strong>Custom settings</strong> to create your own tuning level based on <strong>Write frequency</strong>, <strong>Write contents</strong>, and <strong>Schedule sessions cleanup</strong> settings.</p>-->
|
||
|
|
|
||
|
|
<p><strong>Tuning recommendations</strong></p>
|
||
|
|
|
||
|
|
<p>It is recommended that you follow these guidelines to ensure optimal performance:</p>
|
||
|
|
<ul>
|
||
|
|
<li>In the Session Manager Service, set the Maximum in-memory session count value to a number close to the average number of active sessions. If there are frequent periods where more sessions are active, increasing the base memory value further might improve performance. Also enable Allow overflow.</li>
|
||
|
|
<li>Do not enable persistent sessions unless the application requires them. If persistent sessions are required, enable multi-row sessions.</li>
|
||
|
|
<li>If possible, invalidate finished sessions promptly in your application. Use the javax.servlet.http.HttpSession.invalidate() method to invalidate these sessions. Also set the Invalidation Timeout to the smallest value that is acceptable for your application. If you set it too small, sessions timeout prematurely. You might need to do some testing to determine the appropriate value for your application.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|
||
|
|
|