39 lines
3.0 KiB
HTML
39 lines
3.0 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>Queuing network</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h4><a name="prftuneqnet"></a>Queuing network</h4>
|
||
|
|
|
||
|
|
<p>WebSphere Application Server - Express contains interrelated components that must be tuned to support the custom needs of your e-business application. These adjustments help the system achieve maximum throughput while maintaining the overall stability of the system. This group of interconnected components is known as a queuing network. These queues or components include the network, Web server, Web container, data source, and possibly a connection manager to a custom back-end system. Each of these resources represents a queue of requests waiting to use that resource. Various queue settings include:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li><a href="prftunehttp.htm">IBM HTTP Server</a>: ThreadsPerChild</li>
|
||
|
|
<li><a href="prftuneappsvr.htm#webcont">Web container</a>: Thread pool maximum size, HTTP transports MaxKeepAliveConnections, and MaxKeepAliveRequests</li>
|
||
|
|
<li><a href="prftuneappsvr.htm#data">Data source</a>: Connection pooling and Statement cache size</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p><img src="rzaiz616.gif" width="550" height="211" alt="Queuing network example" border="0"></p>
|
||
|
|
|
||
|
|
<p>Most of the queues that make up the queuing network are closed queues. A closed queue places a limit on the maximum number of requests present in the queue, while an open queue has no limit. A closed queue supports strict management of system resources. For example, the Web container thread pool setting controls the size of the Web container queue. If the average servlet running in a Web container creates 10MB of objects during each request, a value of 100 for thread pools limits the memory consumed by the Web container to 1GB.</p>
|
||
|
|
|
||
|
|
<p>In a closed queue, requests can be active or waiting. An active request is doing work or waiting for a response from a downstream queue. For example, an active request in the Web server is doing work, such as retrieving static HTML, or waiting for a request to be processed in the Web container. A waiting request is waiting to become active. The request remains in the waiting state until one of the active requests leaves the queue.</p>
|
||
|
|
|
||
|
|
<p>All of the Web servers that WebSphere Application Server - Express supports are closed queues, as are WebSphere Application Server - Express data sources. You can configure Web containers as open or closed queues. In general, it is recommended that you use closed queues. If there are no threads available in the pool, a new thread is created for the duration of the request.</p>
|
||
|
|
|
||
|
|
<blockquote>
|
||
|
|
<p><strong><a href="prftuneqtip.htm">Queue configuration tips</a></strong>
|
||
|
|
<br>This topic provides tips to help you tune the queuing network configuration.</p>
|
||
|
|
</blockquote>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|