From: Joshua Slive Date: Sun, 3 Apr 2005 02:11:00 +0000 (+0000) Subject: There is essentially no difference between the "high performance" X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=728fc169f459786c8364fab34a7080865d8100aa;p=thirdparty%2Fapache%2Fhttpd.git There is essentially no difference between the "high performance" config and the normal config, other than being much shorter. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/simple-conf@159866 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/conf/highperformance-std.conf b/docs/conf/highperformance-std.conf deleted file mode 100644 index a8e033c2671..00000000000 --- a/docs/conf/highperformance-std.conf +++ /dev/null @@ -1,70 +0,0 @@ -# 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 - - -MaxClients 150 -StartServers 5 -MinSpareServers 5 -MaxSpareServers 10 - - - -StartServers 2 -MaxClients 150 -MinSpareThreads 25 -MaxSpareThreads 75 -ThreadsPerChild 25 -MaxRequestsPerChild 0 - - -# 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 - - - # 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 - - -# If this was a real internet server you'd probably want to uncomment this: -# -# order allow,deny -# allow from all -# - -# OK that's enough hints. Read the documentation if you want more.