Performance Tuning Siebel Software on the Sun Platform

How is this done?
sdcv480s002:/export/home/sunperf/18306/siebsrvr/admin/%limit stack
stacksize 8192 kbytes
sdcv480s002:/export/siebsrvr/admin/%limit stacksize 1024
sdcv480s002:/export/siebsrvr/admin/%limit stacksize
stacksize 512 kbytes
Please note that a large stack limit can inhibit the growth of the data segment, because
the total process size upper limit is 4Gbytes for a 32-bit application. Also even if the
process stack hasn't grown to a large extent, the virtual memory space will be reserved
for it according to the limit value. While the recommendation to limit stack size to 512
bytes worked well for the workload defined in this paper, this setting may have to be
tweaked for different <strong>Siebel</strong> deployments and workloads. The range could be from 512 to
1024 bytes.
7.4 <strong>Tuning</strong> Sun Java System Web Server
The three main files where tuning can be done are obj.conf, server.xml and
magnus.conf.
Edit magnus.conf:
1. Set the RqThrottle=4028 in the magnus.conf file under the web server
root directory.
2. ListenQ 16000.
3. ConnQueueSize 8000.
4. KeepAliveQueryMeanTime 50.
Edit server.xml:
1. Replaced host name with ip address in server.xml.
Edit obj.conf:
1. Turned off access logging.
2. Turned off cgi, jsp, servlet support.
3. Removed the following lines from obj.conf: ###PathCheck fn="checkacl"
acl="default" and ###PathCheck fn=unix-uri-clean, since
these are not being used by <strong>Siebel</strong>.
<strong>Tuning</strong> parameters used for high user load with Sun Java System Web Servers are
listed in the following table.
<strong>Performance</strong> <strong>Tuning</strong> <strong>Siebel</strong> <strong>Software</strong> on the Sun Platform Page 36