My motivation for writing this module was to limit number of apache children that could simultaneously be serving the (nearly) same resource. The particular instance that spurred my need for this module was an article on the front page of /. that referenced a very long-running, cpu-consuming user process. I wanted to be able to have the site as a whole continue to function adequately and defer requests for the resource once that resource had consumed a certain percentage of all the apache children available.
Current version is 0.2.
Presuming you are using apache 1.3.x, adding in a third-party module is fairly straightforward.
# tar -xf apache_<version>.tar.gz # tar -xf mod_throttle_access.tar.gz # cd apache_<version> # ./configure --add-module=../mod_throttle_access.c ... # make # make install
Syntax: MaxConcurrentReqs
number
Context: directory, .htaccess
Override: Limit
Status: Third Party
Module: mod_throttle_access
Compatibility: Apache 1.3.5 and
above.
The MaxConcurrentRequs directive affects how many clients can concurrently request a given resource.
Example:
<Location "/foo">
<Limit PUT>
MaxConcurrentReqs 10
</Limit>
</Location>
Only 10 requests under the location "/foo" of method PUT can be processed at one time.
Christian Gilmore
$Author: cgilmore $
$Date: 2000/05/09 20:57:47 $
$Id: index.html,v 1.4 2000/05/09 20:57:47 cgilmore Exp $