From owner-freebsd-hackers Fri Dec 15 18:37:37 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA07875 for hackers-outgoing; Fri, 15 Dec 1995 18:37:37 -0800 (PST) Received: from expo.x.org (expo.x.org [198.112.45.11]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA07870 for ; Fri, 15 Dec 1995 18:37:34 -0800 (PST) Received: from exalt.x.org by expo.x.org id AA27724; Fri, 15 Dec 95 21:37:03 -0500 Received: from localhost by exalt.x.org id CAA10865; Sat, 16 Dec 1995 02:37:02 GMT Message-Id: <199512160237.CAA10865@exalt.x.org> To: hackers@freefall.FreeBSD.org Subject: Re: growing X server processes In-Reply-To: Your message of Fri, 15 Dec 1995 11:03:07 EDT. <199512151903.LAA04166@rah.star-gate.com> Organization: X Consortium Date: Fri, 15 Dec 1995 21:37:01 EDT From: "Kaleb S. KEITHLEY" Sender: owner-hackers@FreeBSD.ORG Precedence: bulk > > I guess that it should be interesting to find out exactly what is the > case or the profile that Kaleb mentioned in another posting. I don't know the details about what they did. Perhaps David Dawes, who I know follows this list, might elaborate; but I know that they're in the midst of their beta, compounded by the holiday, so now might not be the best time to get an answer. I expect that it's simply the case that they noticed observed patterns in the memory allocation profile, and they optimized the Xalloc allocator to do better for the most common allocation scenarios. I'm not at liberty to disclose their sources, you'll have to wait for them to release 3.1.3 to see what they did. -- Kaleb