Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (herse.apache.org: domain of pharkins@gmail.com designates
 209.85.132.248 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=cPdOt9Fuoh7pQ4yhcxLHS/FATUTUAyLjQonuqvjjl1UtV9zYCQ42h3PEDQztR2l8dNccq0vpG/1wrVRSb5iAp3Hkd0bd+md5Vvi+EyJ2QXeWbjCTjDz2X8bDuW6ZfrXKWuHH6xeTVNZN8KMdVjxKbE+Xsl1cc6APVlF2WS5mnRY=
Message-ID: <66887a3d0706040730j52f69886x7efb46619b16343d@mail.gmail.com>
Date: Mon, 4 Jun 2007 10:30:12 -0400
From: "Perrin Harkins" <perrin@elem.com>
Sender: pharkins@gmail.com
To: "Jani M." <moogie@iki.fi>
Subject: Re: [mp2] Segmentation faults with threaded worker-mpm
Cc: modperl@perl.apache.org
In-Reply-To: <4663132F.6000507@iki.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4663132F.6000507@iki.fi>

On 6/3/07, Jani M. <moogie@iki.fi> wrote:
> The problems start only when two or more interpreters per
> process is running - unfortunately, this is exactly what I would need
> for scalability and performance.

Are you sure about that?  On Linux, prefork is likely to perform
better.  Threads will use up a lot more memory, and be slow to spawn.
I think you should try a little benchmarking before you put a lot more
time into using threads.

If it turns out you do need to get threads to work, the next step in
fixing segfaults is typically to get a backtrace.  There are
instructions for doing this in the mod_perl docs.

- Perrin