blob: 2d356165166c75e8715a0eb51534e5a515bb983d [file] [log] [blame]
# Ha, you're reading this config file looking for the easy way out!
# "how do I make my apache server go really really fast??"
# Well you could start by reading the /manual/misc/perf-tuning.html
# page. But, we'll give you a head start.
#
# This config file is small, it is probably not what you'd expect on a
# full featured internet webserver with multiple users. But it's
# probably a good starting point for any folks interested in testing
# performance.
#
# To run this config you'll need to use something like:
# httpd -f @@ServerRoot@@/conf/highperformance.conf
Listen 80
ServerRoot @@ServerRoot@@
DocumentRoot @@ServerRoot@@/htdocs
User nobody
# If you're not on Linux, you'll probably need to change Group
Group nobody
<IfModule prefork.c>
MaxClients 150
StartServers 5
MinSpareServers 5
MaxSpareServers 10
</IfModule>
<IfModule worker.c>
MaxClients 8
StartServers 3
MinSpareThreads 5
MaxSpareThreads 10
ThreadsPerChild 25
</IfModule>
# Assume no memory leaks at all
MaxRequestsPerChild 0
# it's always nice to know the server has started
ErrorLog logs/error_log
# Some benchmarks require logging, which is a good requirement. Uncomment
# this if you need logging.
#TransferLog logs/access_log
<Directory />
# The server can be made to avoid following symbolic links,
# to make security simpler. However, this takes extra CPU time,
# so we will just let it follow symlinks.
Options FollowSymLinks
# Don't check for .htaccess files in each directory - they slow
# things down
AllowOverride None
# If this was a real internet server you'd probably want to
# uncomment these:
#order deny,allow
#deny from all
</Directory>
# If this was a real internet server you'd probably want to uncomment this:
#<Directory "@@ServerRoot@@/htdocs">
# order allow,deny
# allow from all
#</Directory>
# OK that's enough hints. Read the documentation if you want more.