Common Server Parameters
Server vendors try to tune their servers as best they can for general use before they send them out to you. They certainly want you to get high performance. The reason you might change things is that you know more about your particular needs than they do.
Number of Processes
You’ll get better performance by
running only the number of server processes your RAM can hold. If you
run too many, you’ll start swapping and performance for each
will drop. If you can run only 32 server processes in RAM, then
don’t try to run any more than that, even if you often have
more than 32 concurrent users. You can configure the number of
httpd processes in Apache with the Max- Clients
directive. You don’t want to
run too few httpd processes either, because you
need enough processes so that fast clients never have to wait for a
slow client to finish and free up a process.
Number of Server Threads
Configure the server only for the maximum number of threads the RAM will support. See Chapter 2, for some threads-to-memory recommendations.
Persistent Connections
Turn
on persistent connections, or keepalives
(KeepAlive
On in Apache’s
httpd.conf ), and set the number of allowed
requests per connection high (MaxKeepAliveRequests
200) to save the overhead of setting up new
connections, but set the timeout fairly low, say 15 seconds
(KeepAliveTimeout
15) to reduce
the impact of dead or very slow clients.
Access Control
The general web performance tip of keeping search paths short takes ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access