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.