Sun Microsystems Sun Java System Web Server 7.0, Manual

Page: 57 / 132

Also, chunked encoding could affect the performance for HTTP 1.1 workload. Tuning the
response buffer size could positively affect the performance. A higher response buffer size in the
configuration's Performance tab
⇒
HTTP tab would result in sending a
Content-length:
header, instead of chunking the response. To set the buffer size using the CLI, use the
wadm
set-http-prop
command's
output-buffer-size
property.
You can also set the buffer size for a Service-class function in the
obj.conf
file, using the
UseOutputStreamSize
parameter.
UseOutputStreamSize
overrides the value set using the
output-buffer-size
property. If
UseOutputStreamSize
is not set, Web Server uses the
output-buffer-size
setting. If the
output-buffer-size
is not set, Web Server uses the
output-buffer-size
default value of 8192.
The following example shows using the CLI to increase the output buffer size, then deploying
the configuration (used if
UseOutputStreamSize
is not specified in
obj.conf
):
./wadm set-http-prop --user=
admin-user
--password-file=
admin-password-file
--config=
config-name
output-buffer-size=16384
./wadm deploy-config --user=
admin-user
--password-file=
admin-password-file
--config=
config-name
The following example shows setting the buffer size for the
nsapi_test
Service function:
<Object name=
"
nsapitest
"
>
ObjectType fn=
"
force-type
"
type=
"
magnus-internal/nsapitest
"
Service method=(GET) type=
"
magnus-internal/nsapitest
"
fn=
"
nsapi_test
"
UseOutputStreamSize=12288
</Object>
Session Creation (Thread) Information
Session (thread) creation statistics are displayed in
perfdump
as follows:
SessionCreationInfo:
------------------------
Active Sessions 128
Keep-Alive Sessions 0
Total Sessions Created 128/128
Active Sessions
shows the number of sessions (request processing threads) currently
servicing requests.
Keep-Alive Sessions
shows the number of HTTP request processing threads serving
keep-alive sessions.
Total Sessions Created
in
perfdump
shows both the number of sessions that have been
created and the maximum threads.
Using Monitoring Data to Tune Your Server
Chapter 2 • Tuning Sun Java System Web Server 57