Apache Performance

Apache Performance

Post by Yibing L » Sun, 05 Nov 2000 10:43:11



Hi,

      We are using Apache 1.3.12 in sun solaris 2.7 for our production
system and we have performance problem due to Apache ( every some time, we
got spikes in the benchmark of request/response time).

      We found this by sending a request to the local machine where Apache
server is running and checking the time of getting the response per request.
We keep sending request every 5 minutes and time the response and find most
of time it take less than 1 second yet there are always a few taking 4,5,7,9
seconds ( this could happen one time within 2 hours, for example, but
irregular).

     We wonder how those spikes happened and whether something in Apache
1.3.12
caused this. I hope someone could give us some help .

      Maybe Apache 1.3.14 can help?

      Thanks,

Yibing Li
Lead Software Architect,
Simplexity.com

 
 
 

Apache Performance

Post by Maurizio Cimasch » Sun, 05 Nov 2000 04:00:00


Packet loss on your network ????
Too much concurrent request on your web server ???? (ie raise the
"MaxClients"/"MaxSpareServers" and lower "KeepAliveTimeOut" if you
have enoght free memory and idle CPU cicle) ????

--
Ciao, Maurizio.

 
 
 

Apache Performance

Post by Yibing L » Mon, 06 Nov 2000 11:27:55


Thanks a lot.
The testing is done in the local machine so it can not be
related to network problem.

It can not be related to too much concurrent request either since each
request is sent every 5 minutes.

But It could be related to conf set-up but I do not know
where to check.

Yibing



> Packet loss on your network ????
> Too much concurrent request on your web server ???? (ie raise the
> "MaxClients"/"MaxSpareServers" and lower "KeepAliveTimeOut" if you
> have enoght free memory and idle CPU cicle) ????

> --
> Ciao, Maurizio.

 
 
 

Apache Performance

Post by Joe Schaefe » Mon, 06 Nov 2000 04:00:00



>       We found this by sending a request to the local machine where Apache
> server is running and checking the time of getting the response per request.
> We keep sending request every 5 minutes and time the response and find most
> of time it take less than 1 second yet there are always a few taking 4,5,7,9
> seconds ( this could happen one time within 2 hours, for example, but
> irregular).

Is it possible you have insufficient RAM? Perhaps your server isn't getting
enough activity to avoid being swapped out to disk? Or maybe it's getting
too much activity, so it has to use swap space to make room for new apache
children?

--
Joe Schaefer

 
 
 

Apache Performance

Post by Yibing L » Mon, 06 Nov 2000 04:00:00


Thank you very much.

From the production manager, I was told that we
have more than enough RAM but I do not know exactly how much we have in that
machine. Suppose we do have more than enough RAM, Will the following still
happen?

Quote:>Perhaps your server isn't getting
> enough activity to avoid being swapped out to disk?

It could be but
How do I check whether this is the case? How to avoid?

Yibing



> >       We found this by sending a request to the local machine where
Apache
> > server is running and checking the time of getting the response per
request.
> > We keep sending request every 5 minutes and time the response and find
most
> > of time it take less than 1 second yet there are always a few taking
4,5,7,9
> > seconds ( this could happen one time within 2 hours, for example, but
> > irregular).

> Is it possible you have insufficient RAM? Perhaps your server isn't
getting
> enough activity to avoid being swapped out to disk? Or maybe it's getting
> too much activity, so it has to use swap space to make room for new apache
> children?

> --
> Joe Schaefer

 
 
 

Apache Performance

Post by steve » Tue, 07 Nov 2000 04:00:00




Quote:> Thank you very much.

> From the production manager, I was told that we
> have more than enough RAM but I do not know exactly how much we have
in that
> machine. Suppose we do have more than enough RAM, Will the following
still
> happen?

You really need to check the state of the server instead of just timing
the responses. Vmstat will show you information pertaining to CPU, mem,
swap useage and more, also look in your error log for possible Apache
warnings. What one person regards as more than enough ram might not be
for another, it all depends what you're serving and how often, but we
don't have that information :)

--
steven

Sent via Deja.com http://www.deja.com/
Before you buy.

 
 
 

1. Apache performance | TCP/IP MSS tweaking?

I was wondering if 'tweaking' (from the Latin: tweakus disastrous) the
TCP/IP setting for the default MSS setting (which is currently 40 on
my RH 7.1 system) is likely to have an appreciable effect on Apache
performance (1.3.22)?

Before I start fooling around (syn: tweaking), thought I'd see if
anyone else has looked at this, or if it isn't really an issue.

Thanks!

2. Samba & CUPS printing solution

3. terrible Apache performance

4. ppp daemon can't get dynamic ip

5. Apache performance mystery

6. what means "IPC$" as share in SAMBA?

7. Poor Apache performance

8. PCI-X hotplug support for Compaq driver

9. Strange Apache performance under AIX (+ DCE)

10. Do a lot of Redirects affect Apache performance?

11. Apache performance monitoring

12. Apache Performance Benchmark

13. Apache Performance on Linux