Here's my understanding of how it works...
Let's say I have 512mb RAM, and each of my apache+mod_perl processes uses an
avg. of 8mb. Ignoring RAM needed for the system stuff (kernel, etc), I can
hold a maximum 512/8=64 processes in memory. Anything more and I'm swapping
to disk.
Now with apache+jserv, if each process is about 2mb (prob. high), with an
ApacheJserv process of about 24mb, I can hold (512-24)/2=244 processes.
So an exlusive apache/jserv solution can serve 3.81x as many conncurrent
connections.
What am I missing?
-mdf
+-----Original Message-----
+From: Dave Paris [mailto:[EMAIL PROTECTED]]
+Sent: Wednesday, July 14, 1999 7:47 AM
+To: Java Apache Users
+Subject: Re: Jserv v.s. mod_perl
+
+
+Mark Foster wrote:
+>
+> In our particular case, jserv is more attractive because the memory
+> footprint of the server processes is much smaller, meaning a
+single head-end
+> can handle as much as 6 or 7 times as many connections. This
+means less
+> head-ends are required to match our traffic load, which
+saves the company
+> money, etc.
+
+I'm sensing a huge logic flaw here.. since when does process size
+directly correlate to system capacity or transactions/second?
+
+ -dsp
+
+
+--
+--------------------------------------------------------------
+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]
+
--
--------------------------------------------------------------
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]
