> You simply cannot come forward and say, "look, I've got this big-assed
> linux box, why is my site sucking?" We don't know, and it's neither our
granted. never my intention.
i described the box only to illustrate that i (should) have sufficient HW.
> The very, very best minds in production architecture out there will pine
> over how much accessing data from RAM sucks - they want all cache, all the
> time. There is not a linear falloff in performance from cache -> RAM ->
> disk, and you should not expect one from the applications which rely on
> those things.
F*** if I care about cache. I just want to stay in RAM (where I can build
my own caches :-)
> The httpd.conf file is extremely well documented. There is a program in
> $APACHE/bin called 'ab,' and will give you a decent baseline from which to
> provision for your site, and etc.
<sigh>
I can see I gave the wrong impression by several miles.
I was never asking, "HOW DO I DO THIS?" I have the same web and same
manpages and same apache/perl/mod_perl source as you do.
I'm a professional. I have a big computing issue. I was asking (other
professionals, who have similar big computing issues):
WHAT DID *YOU* DO?
Hopefully that's more clear. I don't WANT to sound cocky or superior or too
lazy/cool to RTFM. I just want to discuss EXAMPLES of solutions to this
(what seems to be rather common) type of issue.
L8r,
Rob
