How to Boost Web Server Performance: Practical Optimization Strategies

Optimization Thought Overview

To improve web server performance, first understand the three steps of handling a web page request: the browser sends a request, the server locates and returns the page, and the browser renders it. The most performance‑critical step is the server locating the requested content.

Web content can be static or dynamic. Static files are served directly, while dynamic content usually requires an application server (or the web server itself, e.g., IIS for ASP/ASP.NET).

Factors Affecting Page Access

Disk read speed for static pages.

Time to determine static vs. dynamic.

Time to forward the request to the application server.

Application server processing time for dynamic content.

Response time from server to browser.

Server request handling performance.

Network transmission time.

Browser rendering time.

Additional considerations include security policy checks, log file I/O, and concurrent connection count.

Practical Optimization Measures

Based on the analysis, the following actions can improve performance:

Increase bandwidth on both server and client sides.

Accelerate dynamic content processing.

Prefer static content whenever possible (static caching, staticization).

Deploy load‑balanced multiple servers.

Upgrade disk I/O performance.

Reduce HTTP request count.

Upgrade to a higher‑performance web server.

Deploy servers closer to users.

Case Study: Small Forum Site

Site Overview

A Discuz! forum built with PHP + MySQL, ~50 000 registered users, 150 000 – 200 000 daily page views, ~8 000 unique IPs.

Performance Requirements

Home page load time must be cut from ~40 s to under 20 s for domestic users.

Optimization Plan

Move from shared hosting to a dedicated server.

Switch OS from Windows to Linux (Ubuntu).

Replace Apache with Nginx (static files up to 10× faster).

Use eAccelerator for PHP opcode caching (memory‑based, 32 MB cache).

Configure Nginx: 8 worker processes, CPU affinity, gzip compression, 1‑day image cache, 7‑day JS/CSS cache, daily log rotation.

Run PHP‑FPM with 20 processes, using Unix socket for Nginx communication.

Set MySQL storage engine to MyISAM for read‑heavy workload, keep default medium configuration.

Deploy a CDN to serve static assets close to users.

References

Recommended books on web performance, especially “Building High‑Performance Web Sites”.