frank@xxxxx.xxx

[prev] [thread] [next] [Date index for 2004/11/30]

Frank:

/server-status tells the concurrent users. What did you get?

On the other hand, serving 255 concurrent connections means a 
daily unique IP of about 100,000.

I think there are other reasons to use dual-setup. Check
Stas' info page.

--------------------------------------------------

Author:       Frank Wiles <frank@xxxxx.xxx>
Date:         Tue, 30 Nov 2004 14:05:58 -0600

On Tue, 30 Nov 2004 19:41:18 +0000
modperl@xxx.xxx wrote:

> Sites which get number of concurent connections of 200 or 
> more have to use dual-Apache setup (you can't serve such
> number of connections with a single mod_perl server with
> a few G's memory.)

  I disgaree, I've run sites with 256 conncurrent connections
  with a single mod_perl server with 2 GBs of RAM. The reason I
  know it was 256 is because we hit upon a compile time limit 
  under Apache 1.x and we couldn't up the MaxServerChildren any 
  higher without a recompile, but the box certainly could have 
  handled it.

  Unless you're very comfortable in C and the Apach API I think
  you might be better served to performance tune your mod_perl
  setup and/or your application.  

  I'm not saying your way of solving it is bad or anything, just
  that it *can* be done with mod_perl without any C modules. 

        -- 
        Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html