PerformanceTests and Results
Thissection contains the test-specic conguration, tuning, and results for the following tests:
■“StaticContent Test” on page 108
■“DynamicContent Test: Servlet” on page 110
■“DynamicContent Test: C CGI” on page 111
■“DynamicContent Test: Perl CGI” on page 113
■“DynamicContent Test: NSAPI” on page 114
■“PHPScalability Tests” on page 115
■“SSLPerformance Test: Static Content” on page 118
■“SSLPerformance Test: Perl CGI” on page 119
■“SSLPerformance Test: C CGI” on page 120
■“SSLPerformance Test: NSAPI” on page 121
■“E-CommerceWeb Application Test” on page 122
Thefollowing metrics were used to characterize performance:
■Operationsper second (ops/sec) = successful transactions per second
■Responsetime for single transaction (round-trip time) in milliseconds
Theperformance and scalability diagrams show throughput (ops/sec) against the number of
coresenabled on the system.

StaticContent Test

Thistest was performed with a static download of a randomly selected le from a pool of 10,000
directories,each containing 36 les ranging in size from 1KB to 1000 KB. The goal of the static
contenttest was to saturate the cores and nd out the respective throughput and response time.
Thistest used the following conguration:
■Staticles were created on striped disk array (Sun StorEdge 3510).
■Multiplenetwork interfaces were congured.
■WebServer was congured with 64 bit.
■File-cachewas enabled with the tuning settings described in the following table.
PerformanceTestsand Results
SunJavaSystem Web Server 7.0 Update 1 Performance Tuning,Sizing, and Scaling Guide •108