Return-Path: Delivered-To: apmail-perl-modperl-archive@www.apache.org Received: (qmail 89598 invoked from network); 16 Mar 2007 16:11:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Mar 2007 16:11:00 -0000 Received: (qmail 98401 invoked by uid 500); 16 Mar 2007 16:11:01 -0000 Delivered-To: apmail-perl-modperl-archive@perl.apache.org Received: (qmail 98388 invoked by uid 500); 16 Mar 2007 16:11:01 -0000 Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list modperl@perl.apache.org Received: (qmail 98372 invoked by uid 99); 16 Mar 2007 16:11:01 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Mar 2007 09:11:01 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [208.97.132.145] (HELO swarthymail-a2.g.dreamhost.com) (208.97.132.145) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Mar 2007 09:10:48 -0700 Received: from [192.168.1.100] (user-108763e.cable.mindspring.com [64.131.152.110]) by swarthymail-a2.g.dreamhost.com (Postfix) with ESMTP id 4C43AF05FD; Fri, 16 Mar 2007 09:10:27 -0700 (PDT) In-Reply-To: <897881.17662.qm@web57913.mail.re3.yahoo.com> References: <897881.17662.qm@web57913.mail.re3.yahoo.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <3686E50B-6267-4716-9C53-8F66CCD3A615@2xlp.com> Cc: mod_perl list Content-Transfer-Encoding: 7bit From: Jonathan Vanasco Subject: Re: mod_perl implementation possibility Date: Fri, 16 Mar 2007 12:10:01 -0400 To: James.L X-Mailer: Apple Mail (2.752.2) X-Virus-Checked: Checked by ClamAV on apache.org On Mar 16, 2007, at 11:55 AM, James. L wrote: > any special setup for mod_perl 1 + apache 1 under > virtual host? it works but my impression is that it is > hard to setup and must be coded very carefully. > > that's probably the reason why i rarely see mod_perl > offered in share dhosting environment. no, mod_perl is just unsuitable for shared hosting by design. it has nothing to do with virtual hosts. a- mp caches code into apache. it can take *a lot* of ram. there's no effective way to manage memory in these situations -- you either preload everyone's stuff into apache at start, or apache takes a performance hit each time a child reads code for the first time. because apache children expire after x requests, in a shared environment you'll get almost no speedup - and a potential performance decrease. b- as clinton noted previously, the way mod_perl handles namespaces can cause overlap issues As I said before, you're best off to just install apache2 and mp2 *in addition to apache1*. you can keep all your apache1 stuff running as- is on port 80. just run/configure apache2/mp2 to run on an alternate port - like 8080 , and proxy the necessary requests to it via mod_proxy on 80. // Jonathan Vanasco | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | SyndiClick.com | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | FindMeOn.com - The cure for Multiple Web Personality Disorder | Web Identity Management and 3D Social Networking | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | RoadSound.com - Tools For Bands, Stuff For Fans | Collaborative Online Management And Syndication Tools | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -