From owner-freebsd-questions@FreeBSD.ORG Wed Aug 24 17:26:14 2005 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F3B416A41F for ; Wed, 24 Aug 2005 17:26:14 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id E949A43D48 for ; Wed, 24 Aug 2005 17:26:13 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id j7OHQD1Y052622; Wed, 24 Aug 2005 12:26:13 -0500 (CDT) (envelope-from dan) Date: Wed, 24 Aug 2005 12:26:13 -0500 From: Dan Nelson To: Lei Sun Message-ID: <20050824172613.GC88693@dan.emsphone.com> References: <20050824143133.GA88693@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 5.4-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.9i Cc: questions@freebsd.org Subject: Re: oversized httpd process? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Aug 2005 17:26:14 -0000 In the last episode (Aug 24), Lei Sun said: > Now that I think about it, I did install the eaccelerator for php, > and configured it to take 128Mb for eaccelerator.shm_size. It also > appears that when I reboot the machine A without pointing my browser > to it once, the httpd processes are quite small. BUT... > > Even with the 2 php application that I installed (phpmyadmin, > mediawiki), I don't think there should be that much caching going on. > Since if I add the total size of the 2 application together, they > won't even hit 20MB. In other words, my understanding would be: even > if eaccelerator wants to cache them all, eaccelerator wouldn't be > able to find that much stuff to cache, and it would always be less > than 20MB. Apparently eaccellerator mmaps the entire shm segment whether it is currently using it or not. -- Dan Nelson dnelson@allantgroup.com