From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24930 invoked by alias); 23 Nov 2006 16:18:40 -0000 Received: (qmail 24918 invoked by uid 22791); 23 Nov 2006 16:18:39 -0000 X-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 23 Nov 2006 16:18:32 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id kANGIU0j028225 for ; Thu, 23 Nov 2006 11:18:30 -0500 Received: from pobox.toronto.redhat.com (pobox.toronto.redhat.com [172.16.14.4]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id kANGIUaK013591 for ; Thu, 23 Nov 2006 11:18:30 -0500 Received: from [172.16.14.160] (tow.toronto.redhat.com [172.16.14.160]) by pobox.toronto.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id kANGITVd031850 for ; Thu, 23 Nov 2006 11:18:29 -0500 Subject: Re: Announcing new interface: FindProc From: Nurdin Premji To: frysk In-Reply-To: <1164241351.3097.14.camel@tow.toronto.redhat.com> References: <1163802149.3483.5.camel@tow.toronto.redhat.com> <4561C33B.4010907@redhat.com> <1164038923.3018.4.camel@tow.toronto.redhat.com> <1164241351.3097.14.camel@tow.toronto.redhat.com> Content-Type: text/plain Date: Thu, 23 Nov 2006 16:18:00 -0000 Message-Id: <1164298709.19752.13.camel@tow.toronto.redhat.com> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1.1 (2.8.1.1-3.fc6) Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2006-q4/txt/msg00226.txt.bz2 > Preliminary reports show that make check times have decreased from > 1m7.522s to 1m0.825s. > > I also tested fstack and fcore and the results are: > > fstack: down from 2.3314 to 2.2094. > fcore: up from 1.4858 to 2.0045. * > > There were some weird issues with fcore as shown below by actual > numbers: > > Old fstack: 2.225, 2,385, 2.184, 2,666, 2,194 > New fstack: 2.305, 2.161, 2.263, 2.164, 2.154 > > Old fcore: 1.504, 1.389, 1.036, 1.935, 1.599, 1.440 > New fcore: 1.327, 3.355*, 1.019, 4.353*, 0.996, 0.978 > > (So technically fcore would have been much faster but for the anomalies) > > I was not running these tests in single user mode which would probably > explain the anomalies, so tomorrow morning I'm going to read up on > single user mode and try to post more accurate numbers. By the way, the above tests where done on evolution. Secondary measurements in single user mode show the following. On a sleeping funit-child with 12 threads: fstack: up from 1.5915 to 1.596 fcore: up from 1.039 to 1.265 which is even weirder, but the numbers show that in general new is better than old: Old fstack: 1.616, 1.626, 1.456* 1.616, 1.621, 1.614 New fstack: 1.593, 1.593, 1.593, 1.601, 1.598, 1.600 Except for the old fstack getting a burst of speed in the middle there, the new method is consistently faster. Old fcore: 0.479, 1.423*, 0.451, 0.933*, 0.968*, 1.977* New fcore: 0.429, 0.429, 3.106*, 0.433, 2.754*, 0.437 Here again we have weird hangs at odd times. I don't know why.