5

Set priority for specific requests in Apache webserver

view full story
linux-howto

http://serverfault.com – we have a website with CometChat integration for our users; since our apache server gets a lot of requests for the chat service, we'd like to set a different (lower) priority for these requests, while serving with an higher priority the other ones. As far as we know, one way to do this could be using mod_qos, that would let us limit the number of requests in a period of time (eg reqs per second) for a specific path. This is not exactly what we'd like to do, but could be a partial solution. My question is: is there a better solution to prioritize requests? If you suggest to use mod_qos, which (HowTos)

taskli's picture
Submitted by taskli on 07/19/2012 – Made popular on 07/19/2012

Stories similar to Set priority for specific requests in Apache webserver

Maybe I'm going about this the wrong way, but it seems like it would be a good idea to limit maximum requests per second on a per IP address basis for an Apache server.

I've seen the results before (over-limit warnings), especially for things like APIs which can easily get flooded with requests.

Two dedicated separate servers running with identical configuration of hardware (Dual E5-2620 32GB) in similar environment (CentOS 6.3, Apache+PHP+MySQL) serving similar tasks, but behaving in different way of processing Apache web server - CPU usage 17x times bigger in server which has lower requests.

CPU Usage: u2.03 s1.05 cu316.97 cs0 - 4.35% CPU load 11.9 requests/sec - 5.3 kB/second - 4

In a short question: If 10 requests hit Apache, does it process them one by one, so when R3 finishes, then it starts to run R4, or does it fire 10 processes/threads/whatever and are resolved simultaneously?

Now some background: I have a PHP script that takes up to two minutes to do some processes.

I have a hardware firewall between the internet and an Ubuntu 8.04 LTS system.

I am seeing requests come out of the Ubuntu system that are port 53 UDP packets (DNS requests) going to many different IP addresses (not just my registered DNS server).

I am trying to calculate the average requests per seconds for a specific period of time of my Apache logs.

I have been able to narrow the results down to the period I am interested in, as well as calculating the requests per second, but I am not able to calculate the average.

With a server running Apache and PHP via mod_fcgid, I'd like to log all requests handled by PHP into a separate file so that I can get a better idea of which requests are going through PHP versus being handled directly through the filesystem.

This is a site with some pretty complex rewrite rules in .htaccess (Wordpress with W3 Total Cache), which translates cached PHP requests into static file re

Awesome Apache Monitoring 25 weeks 5 days ago

I'm doing some research into how I can collect and graph useful statistics from apache per vhost:

Bandwidth Usage Number of requests Errors Busy workers Free workers Queued/Waiting requests

Bonus points for solutions including average performance for:

Request time Requests / second Requests per keep alive connection All of the above overall rather than per vhost

I've been spoiled by awesom

My site on Webfaction is using the Requests python package to make a good number of requests to another site. This happens whenever a user triggers a particular ajax request on mine.

Server is a standard LAMP stack configured via cpanel on CentOS 5.9.

We have one file, call it bad.php, on one of our domains that is mistakenly being accessed about 10 times a second by a service provider. The file no longer exists, and we want to block these requests in the most efficient way possible.