Re: Apache Performance Problem

[Bill Stoddard <bi...@wstoddard.com>]

Sounds like you are running out of Apache processes and connections are
getting backed up in the TCP/IP stack's listen queue (on your non-SSL port).
You will still get quick responses on ports that don't have much traffic.
I'd recommend uping maxclients and see what happens.

Bill

> apache version 1.3.4
>
> We have a E3500 Sun solaris server with 8 processors 8 Gig Ram. When
traffic
> is high and the CPU traffic creaps up, (40% idle) but I/O wait is 0% to
10%
> the HTML serving from the file system is very slow.
> Now, we also have https apache on the box and calling the same page from
it
> is fast. The server processes 80% CGI and 20% html. I was looking at
moving
> to Apache 2.0 but am not sure it will help as I suspect a configuration
> problem here. We have 100 max procs and 20 minimum. I don't think this is
it
> because we have a 50 max clients and it does not max out. Also, it
connects
> quickly to the socket, but serves the page slowly.
>
> Mike Haines
> mhaines@seqtek.com
>

Re: Apache Performance Problem

[Mike Haines <mh...@seqtek.com>]

That was it, thanks.

Mike Haines

----- Original Message -----
From: "Bill Stoddard" <bi...@wstoddard.com>
To: <ne...@apache.org>
Sent: Wednesday, November 22, 2000 9:37 AM
Subject: Re: Apache Performance Problem


> Sounds like you are running out of Apache processes and connections are
> getting backed up in the TCP/IP stack's listen queue (on your non-SSL
port).
> You will still get quick responses on ports that don't have much traffic.
> I'd recommend uping maxclients and see what happens.
>
> Bill
>
> > apache version 1.3.4
> >
> > We have a E3500 Sun solaris server with 8 processors 8 Gig Ram. When
> traffic
> > is high and the CPU traffic creaps up, (40% idle) but I/O wait is 0% to
> 10%
> > the HTML serving from the file system is very slow.
> > Now, we also have https apache on the box and calling the same page from
> it
> > is fast. The server processes 80% CGI and 20% html. I was looking at
> moving
> > to Apache 2.0 but am not sure it will help as I suspect a configuration
> > problem here. We have 100 max procs and 20 minimum. I don't think this
is
> it
> > because we have a 50 max clients and it does not max out. Also, it
> connects
> > quickly to the socket, but serves the page slowly.
> >
> > Mike Haines
> > mhaines@seqtek.com
> >
>
>