From owner-freebsd-questions@FreeBSD.ORG Thu Jan 19 11:16:53 2006 Return-Path: X-Original-To: freebsd-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 1D7B816A41F for ; Thu, 19 Jan 2006 11:16:53 +0000 (GMT) (envelope-from user@celeritystorm.com) Received: from mail.celeritystorm.com (213-247-62-79.ip.netshark.nl [213.247.62.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id B322B43D45 for ; Thu, 19 Jan 2006 11:16:52 +0000 (GMT) (envelope-from user@celeritystorm.com) Received: by mail.celeritystorm.com (Postfix, from userid 106) id 1045E3D8C3C; Thu, 19 Jan 2006 12:34:26 +0100 (CET) Received: from [192.168.0.1] (unknown [81.84.174.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.celeritystorm.com (Postfix) with ESMTP id AE86F3D756B for ; Thu, 19 Jan 2006 12:34:21 +0100 (CET) Message-ID: <43CF752A.6080507@celeritystorm.com> Date: Thu, 19 Jan 2006 11:16:58 +0000 From: "M. L." User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040724) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Apache & PV entries 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: Thu, 19 Jan 2006 11:16:53 -0000 Hello list, I am configuring a very heavily used apache webserver, that required some special needs. This particular configuration needs to have at least 1024 httpds always running. Reaching this number is not a problem, but whenever I stop apache via apachectl stop, I notice all the httpds take a long time (1 min) to vanish - and meanwhile, top shows most of them locked. The states I see in top are: *vm ob RUN while the header shows: 1038 processes:332 running, 12 sleeping, 694 lock The numbers vary a lot. Eventually, they get killed, but it takes too much time. After some searching, I found out the cause for this was running out of PVs. I've added the following relevant options to the kernel: options KVA_PAGES=768 options PMAP_SHPGPERPROC=5120 sysctl vm.zone | grep PV shows: (note: httpd stopped here) (limit) (used) (free) (requests) PV ENTRY: 24, 84410445, 5522, 1632543, 5381679 So, if my assumptions are correct, and running out of PVs was the cause (I did get that message about increasing PMAP_SHPGPERPROC before I placed that in the kernel), there is a problem now. If you look at the vm.zone output, there are 84,410,445 PVs that could exist, but the system shows only 1,632,543 free. This leads me to believe there is another thing to tune. I already have a high PVs limit, but according to this output, it's not going further than 1,6 millions. My question is, what can I do to make the system use the full 84 millions, as I have not found any way to do this.