Download file [1]

# 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 [1]@@/conf/highperformance.conf

Listen [1] 80
ServerRoot [1] @@ServerRoot [1]@@
DocumentRoot [1] @@ServerRoot [1]@@/htdocs

User [1] nobody
# If you're not on Linux, you'll probably need to change Group [1]
Group [1] nobody

MaxClients [1] 150
StartServers [1] 5
MinSpareServers [1] 5
MaxSpareServers [1] 10

StartServers [1] 2
MaxClients [1] 150
MinSpareThreads [1] 25
MaxSpareThreads [1] 75
ThreadsPerChild [1] 25
MaxRequestsPerChild [1] 0

# Assume no memory leaks at all
MaxRequestsPerChild [1] 0

# it's always nice to know the server has started
ErrorLog [1] logs/error_log [1]

# Some benchmarks require [1] logging, which is a good requirement. Uncomment
# this if you need logging.
#TransferLog [1] logs/access_log [1]

# 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 [1] FollowSymLinks

# Don't check for .htaccess files [1] in each directory [1] - they slow
# things down
AllowOverride [1] None

# If this was a real internet server you'd probably want to
# uncomment these:
#order [1] deny [1],allow [1]
#deny [1] from all

# If this was a real internet server you'd probably want to uncomment this:
#
# order [1] allow [1],deny [1]
# allow [1] from all
#

# OK that's enough hints. Read the documentation if you want more.

Vote Result

Score: 0.0, Votes: 0

Bookmark/Search this post with:

[2] | [3] | [4] | [5] | [6] | [7] | [8]