Excerpt from the mod_perl performance tuning guide:
"The primary way to achieve maximal performance is to reduce the resources
consumed by the mod_perl enabled HTTPD processes."
...
+-----Original Message-----
+From: Dave Paris [mailto:[EMAIL PROTECTED]]
+Sent: Wednesday, July 14, 1999 9:04 AM
+To: Java Apache Users
+Subject: Re: Jserv v.s. mod_perl
+
+> What am I missing?
+
+Little things like processor power, application design, database speed,
+query construction/optimization, SSL, application speed, speed of the
+network, speed of remote data sources, and on, and on, and on.
+
+The only thing you're referring to is how many processes you can fit
+into memory - which has nothing to do with capacity.
Certainly they are only part of the system. Being that, they are also
a(nother) potential bottleneck in the number of users that can access a
website at once.
+
+If your design is poor/slow .. or if a query takes awhile to run .. or
+you have lacking processor power .. or if you're dependant on remote
+data sources...
+.. you still won't be getting anywhere with 244 of those processes
+sitting in memory. If anything, you'll REDUCE your performance by
+filling memory with these processes, leaving no spare space for other
+storage needs.
+
+A few, well-designed, optimized processes will do MUCH more than many
+poorly designed, inefficient ones will.
+(note: I'm not flogging any particular language .. just your
+assumptions
No problem. I've found some great information at the following links, in
case you haven't seen them:
http://perl.apache.org/guide/
http://perl.apache.org/tuning/
I've also found the book "Web Performance Tuning" (O'Reilly) to be helpful.
-mdf
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
READ THE FAQ!!!! <http://java.apache.org/faq/>
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
