Return-Path: X-Original-To: apmail-perl-modperl-archive@www.apache.org Delivered-To: apmail-perl-modperl-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AF2ADED12 for ; Sat, 19 Jan 2013 21:00:43 +0000 (UTC) Received: (qmail 54227 invoked by uid 500); 19 Jan 2013 21:00:42 -0000 Delivered-To: apmail-perl-modperl-archive@perl.apache.org Received: (qmail 54194 invoked by uid 500); 19 Jan 2013 21:00:42 -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 54183 invoked by uid 99); 19 Jan 2013 21:00:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 Jan 2013 21:00:42 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.220.182] (HELO mail-vc0-f182.google.com) (209.85.220.182) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 Jan 2013 21:00:35 +0000 Received: by mail-vc0-f182.google.com with SMTP id fl17so764077vcb.13 for ; Sat, 19 Jan 2013 13:00:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=x5cSep4qTYK7Tboq5yeKZFk9CAnLiv6O9vhfws1ksXQ=; b=dVLkLNyOfSJ62JIrrJkhctsX6dNhGDV8jtyMk9zMhvSMVvgKHHI3Yr7e4rBGV5dquq EbIrYGReGlLiIPdru7QmFzcMORk5Y6MlbTFWsPXPJ+anho5Yq8s8KSknpqEOG7SYq1qm BHE3HTzLQ5+mlh5r5Tov0cBaa3R/oWoaUfCVwq++a2cvuwbLhhztPxV/j8HPCguYpArr oWWTYSMUiYCZMK9DO8WJKIP6YcBIQvkUaALeIOi6y8zyQbJaCPJZybh4mduRVBXhbkI7 /h4vEF3qxw6yKvGKbh8AzrHDfti/taVDYyk12TT49BC5+IattVdGzT/RUcl0pP4FnS57 xMsA== MIME-Version: 1.0 X-Received: by 10.52.29.40 with SMTP id g8mr12655355vdh.58.1358629214376; Sat, 19 Jan 2013 13:00:14 -0800 (PST) Received: by 10.58.23.170 with HTTP; Sat, 19 Jan 2013 13:00:14 -0800 (PST) In-Reply-To: References: Date: Sat, 19 Jan 2013 13:00:14 -0800 Message-ID: Subject: Re: mod_perl2 memory problem From: Fred Moyer To: Idel Fuschini Cc: modperl List Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQnyX2em5ySpi9q6QsU1owP6SNb7xxwu68b/z+pfLbctaqOq/1sW2PUjgchPYablC2FaEmpR X-Virus-Checked: Checked by ClamAV on apache.org On Sat, Jan 19, 2013 at 12:45 PM, Idel Fuschini wrote: > Hi all, > I have compiled apache webserver with this configuration: > > ./configure --prefix=/foo/apache-2.2.23-worker-1st --enable-modules=all > --enable-mods-shared=all --disable-ipv6 --enable-ssl > --with-ssl=/foo/openssl-1.0.1c --enable-proxy --enable-proxy-connect > --enable-proxy-http --with-mpm=worker --enable-cgi > > without mod_perl without mod_perl each httpd process take 12m > > with mod_perl each httpd process takes 38m > > and each request the memory increase the memory. Either you are not loading all your modules into the parent httpd process at startup time (startup.pl, process growth is code), or your processes are setting globals that hold data from request handling (process growth is data related. If you can test on Solaris or OS X, I recommend running iosnoop (a dtrace script) which will identify what files your application touches. If you see your application accessing modules after the app has started, put those modules in startup.pl Although, 38 megabytes is small. I work with applications that have 512+ megabyte process footprints. > > mod_perl version is 2.0.5. > > Thanks > idel