Server Farms
The clustering features of Web Server allow you to easily deploy to a server farm. Because all
servers in a server farm share identical congurations, tuning is not done on a server-by-server
basis.
64–Bit Servers
The performance for the 64–bit Web Server is not necessarily better than the performance for
the 32–bit Web Server, but the 64–bit server scales better. Because the 32–bit Web Server
process is conned to 4 GB of address space, it can run out of address space attempting to
support simultaneous sessions beyond a certain limit. Even if the host machine has available
memory and CPU resources, the 32–bit Web Server might not be able to take advantage of it
because of the address space limit. The 64–bit Web Server can run more applications and
servlets than the 32-bit server. Also, the 64–bit Web Server can cache several GBs of static
content, while the 32-bit Web Server is conned to 4 GB of address space.
In general, the tuning for the 64–bit Web Server is similar to the tuning for the 32–bit Web
Server. The dierences are mostly tuned at the operating system level. Tuning specics are
discussed in
“Tuning UltraSPARC T1–Based Systems for Performance Benchmarking” on
page 97
.
SSL Performance
SSL always has a signicant impact on throughput, so for best performance minimize your use
of SSL, or consider using a multi-CPU server to handle it.
For SSL, the Web Server uses the NSS library. However, there are other options available for
SSL:
■
If you are using the Solaris 10 operating system, kernel SSL (KSSL) is available. It does not
contain all the algorithms available, as does NSS, but it often provides better performance.
■
A cryptographic card hardware accelerator for SSL can also improve performance.
■
If you are using the 64–bit Web Server on Solaris, you can use the cryptographic accelerator
of the UltraSPARC T1 processor.
SSLPerformance
Chapter1 • Performanceand MonitoringOverview 21