Maxage; Flushinterval; Smallfilesizelimit; Improving Servlet Performance - Sun Microsystems Netscape Enterprise Server Administrator's Manual

Improving Servlet Performance

MaxAge

Set MaxAge based on whether the content is updated (existing files are
modified) on a regular schedule or not. For example, if content is updated four
times a day at regular intervals, MaxAge could be set to 21600 seconds (6
hours). Otherwise, consider setting MaxAge to the longest time you are willing
to serve the previous version of a content file, after the file has been modified.

FlushInterval

Set FlushInterval to a short enough time that the cache does not become
full of expired entries.

SmallFileSizeLimit

The idea of distinguishing between small files and medium files is to avoid
wasting part of many pages of virtual memory when there are lots of small files.
So the SmallFileSizeLimit would typically be a slightly lower value than
the VM page size.
Improving Servlet Performance
The use of NSAPI cache will improve servlet performance in cases where the
obj.conf configuration file has many directives. To enable NSAPI cache
inlcude the following line in obj.conf:
It's advisable to have servlet engine NameTrans (NameTrans
fn="NSServletNameTrans" name="servlet") to be the first in the list.
It uses highly-optimized URI cache for loaded servlets and will return
REQ_PROCEED if the match is found, thus eliminating the need of other
NameTrans directives to be executed.
jvm.conf/jvm12.conf has a configuration parameter, called
jvm.stickyAttach. Setting the value of this parameter to "1" will cause threads to
remember that they are attached to the JVM, thus speeding up request
processing by eliminating AttachCurrentThread and
DetachCurrentThread calls. It can however have a side-effect as recycled
254 Netscape Enterprise Server Administrator's Guide
Init fn="nsapi-cache-init" enable=true