From owner-freebsd-current@FreeBSD.ORG Thu Feb 23 21:00:16 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBD1116A420 for ; Thu, 23 Feb 2006 21:00:16 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D90A43D66 for ; Thu, 23 Feb 2006 21:00:16 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 78F3D46BD8; Thu, 23 Feb 2006 15:59:59 -0500 (EST) Date: Thu, 23 Feb 2006 21:04:11 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Peter Fraser In-Reply-To: Message-ID: <20060223205739.P33959@fledge.watson.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: Virtual memory consumption (both user and kernel) in modern CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2006 21:00:16 -0000 On Thu, 23 Feb 2006, Peter Fraser wrote: > It's truly a ptiy that so serious a thing is an issue so near to a release. > I agree that users should be given a choice especially since some of us run > non-threaded apps that spawn a number of processes. From what I have read, > wouldn't a squid + squidguard combination rely much more heavily on swap > now. If so, I think I will also stick with the 5 series and 6.0 in my > environment. If I read your e-mail right, you're referring to reported issues regarding the new user space malloc implementation in 7.x. However, the 7.0 release is still well over a year away. The new malloc implementation is not present in 6.x, and I wouldn't expect a merge to the 6.x branch any time soon, if ever. Unless you were planning to run 7.x in production in the next year, something I generally wouldn't recommend without very careful consideration, I'm not sure how this affects your decision regarding FreeBSD versions to run -- neither of the upcoming FreeBSD 5.5 or FreeBSD 6.1 releases would be affected in any way. Perhaps there has been a misunderstanding? Robert N M Watson