Very Computer

< snip >

Quote:> * Our sites are very dynamic with each page being built as it is requested.
> We would probably NOT take advantage of the kernel-cache enhancements of the
> IBM HTTP-server.

My first guess is that the CGI fork/exec() overhead is killing you .

I'd suggest a look at Fast CGI in the Apache Manuals ... our system is
extremely dynamic, and we were able to support several orders of
_magnitude_ more requests per second when we changed the interface
from plain CGI to FastCGI.

Quote:> So what do we do now. We have bought a very expensive system that we were
> promised would handle much more traffic than it seems to do. Is there any
> tweaks we can do to get better performance?

--
#include  <disclaimer.std>    /* I don't speak for IBM ...           */
                              /* Heck, I don't even speak for myself */
                              /* Don't believe me ? Ask my wife :-)  */

Quote:

> My first guess is that the CGI fork/exec() overhead is killing you .

> I'd suggest a look at Fast CGI in the Apache Manuals ... our system is
> extremely dynamic, and we were able to support several orders of
> _magnitude_ more requests per second when we changed the interface
> from plain CGI to FastCGI.

Thanks for your input Richard, even though it doesn't help us much. We
use PHP and not CGI.

Also, to be able to handle the load for now, we have temporarily
installed a Linux-box - PIII-600 MHz, 768 MB memory - next to the
H70:s. And that Linux-box seems to be able to handle considerably more
requests than a single H70.

/Per

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

BTW, I didn't ask, but are you current on AIX maintenance ? There's
been quite a few IP related fixes in both AIX 4.3.2 and 4.3.3. I
wouldn't consider running anything lower than Maintenance Level 2 on
either release.

--
#include  <disclaimer.std>    /* I don't speak for IBM ...           */
                              /* Heck, I don't even speak for myself */
                              /* Don't believe me ? Ask my wife :-)  */

Quote:

> My first guess is that the CGI fork/exec() overhead is killing you .

> I'd suggest a look at Fast CGI in the Apache Manuals ... our system is
> extremely dynamic, and we were able to support several orders of
> _magnitude_ more requests per second when we changed the interface
> from plain CGI to FastCGI.

Thanks for your input Richard, even though it doesn't help us much. We
use PHP and not CGI.

Also, to be able to handle the load for now, we have temporarily
installed a Linux-box - PIII-600 MHz, 768 MB memory - next to the
H70:s. And that Linux-box seems to be able to handle considerably more
requests than a single H70.

/Per

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

BTW, I didn't ask, but are you current on AIX maintenance ? There's
been quite a few IP related fixes in both AIX 4.3.2 and 4.3.3. I
wouldn't consider running anything lower than Maintenance Level 2 on
either release.

--
#include  <disclaimer.std>    /* I don't speak for IBM ...           */
                              /* Heck, I don't even speak for myself */
                              /* Don't believe me ? Ask my wife :-)  */

The two are not necessarily mutually exclusive.

1. Check you're using mod_php and haven't built PHP to run through CGI.
Check the output from phpinfo() to check what modules are loaded.

2. I may be on the wrong track here, but I'd suggest using IBM's
C-compiler on the AIX system rather than the gcc compiler. It has true
64-bit support and may well produce better binaries the the gcc version.
If you don't want to buy it, maybe you could get someone else to do the
compile for you.

Regards,

Martin Shields.