From owner-freebsd-questions@FreeBSD.ORG Tue May 24 07:06:08 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 46B701065670 for ; Tue, 24 May 2011 07:06:08 +0000 (UTC) (envelope-from griffin@gnix.co.uk) Received: from think.gnix.co.uk (griffin.gnix.co.uk [80.229.5.32]) by mx1.freebsd.org (Postfix) with ESMTP id B2F558FC12 for ; Tue, 24 May 2011 07:06:07 +0000 (UTC) Received: from think.gnix.co.uk (localhost [127.0.0.1]) by think.gnix.co.uk (8.14.4/8.14.4) with ESMTP id p4O7659N011942 for ; Tue, 24 May 2011 08:06:05 +0100 (BST) (envelope-from griffin@gnix.co.uk) Received: (from jpg@localhost) by think.gnix.co.uk (8.14.4/8.14.4/Submit) id p4O765iB011941 for freebsd-questions@freebsd.org; Tue, 24 May 2011 08:06:05 +0100 (BST) (envelope-from griffin@gnix.co.uk) X-Authentication-Warning: think.gnix.co.uk: jpg set sender to griffin@gnix.co.uk using -f Date: Tue, 24 May 2011 08:06:05 +0100 From: Jamie Paul Griffin To: freebsd-questions@freebsd.org Message-ID: <20110524070605.GA1215@think.gnix.co.uk> References: <20110523202020.GB75878@think.gnix.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-PGP-Key: http://gnix.co.uk/jpg-pubkey.asc X-Operating-System: FreeBSD 8.2-RELEASE User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: perl-threaded X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 May 2011 07:06:08 -0000 On Mon, May 23, 2011 at 05:50:39PM -0400, Alejandro Imass wrote: > Not necessarily, many cpan modules are either thread unaware/innocuous > or thread safe, though there are exceptions. > I have re-compiled Perl with threads with pre-installed libraries and > never had a problem. > > You will surely know which things fail when they blow-up or leak you > to death, when you use threading of course. Especially long-running > software like mod_perl. But for that, you always have > maxrequestsperchild ;-) > > Now that I mention it, mod_perl would probably need rebuilding IMHO > just to be on the safe side, wherever _that_ is with threads ;-) > > Joking aside, I have scaled tremendously with apache mod_perl + > mod_worker a rare but exquisite high-scale Web software recipe. Hi Alejandro - I did encounter a few issues, rebuilt them all and it's good. Thanks for your reply. jamie