From owner-freebsd-sparc64@FreeBSD.ORG Mon Aug 11 08:51:05 2003 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31FEA37B401; Mon, 11 Aug 2003 08:51:05 -0700 (PDT) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E7C443F93; Mon, 11 Aug 2003 08:51:04 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.12.9/8.12.9) with ESMTP id h7BFp2Cx027913; Mon, 11 Aug 2003 11:51:02 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20030809084019.GA4704@rot13.obsecurity.org> References: <20030807062536.GA68747@dragon.nuxi.com> <20030809084019.GA4704@rot13.obsecurity.org> Date: Mon, 11 Aug 2003 11:51:00 -0400 To: Kris Kennaway From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) cc: sparc64@freebsd.org Subject: Re: ponderous 'make world' times post GCC 3.3... X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Aug 2003 15:51:05 -0000 At 1:40 AM -0700 8/9/03, Kris Kennaway wrote: >On Sat, Aug 09, 2003, Garance A Drosihn wrote: > >> So, apparently the problem is something a bit more subtle than >> just gcc 3.3 being slower to compile than gcc 3.2. Apparently >> the August 9th system is a lot slower at *running* than the >> early system. Do we have some other benchmarks we could run? > >This suggests that something might have been pessimized with >the gcc 3.3 code generation on sparc. Well, I'm thinking that maybe we're blaming the wrong thing for this slowdown. I have the results for a few more builds: realtime user sys ---------- ------------- ------------ build 1: 347m 33.407s 283m 0.162s 53m 45.805s build 2: 387m 4.205s 315m 25.441s 59m 44.648s build 3: 1238m 11.386s 1064m 31.148s 136m 54.366s build 4: 384m 30.479s 312m 54.407s 59m 7.338s build 1 is the cvsup'ed from July 6th, being built on top of a world from June 6th. build 2 is the cvsup'ed source from August 7th, built on top of the world from June 6th (apparently I never installed the buildworld from July 6th). build 3 is the exact same source as build #2, built on the world that was installed by build 2. build 4 is where I took the kernel from build #1 (which was sitting in /boot/kernel.old), and booted off of that. So, the system is running the kernel from June 6th, but the entire userland is from August 7th. This means it starts out with gcc (GCC) 3.3.1 [FreeBSD] 20030711 (prerelease). So, the slowdown is completely in the kernel. Either there was some change made to the kernel-sources which has caused the slowdown, or there is something about gcc 3.3.1's code generation such that we end up with a horrendously slower kernel. But it isn't gcc 3.3.1 *itself* which is that much slower at compiling. I don't know where the slowdown is occurring. Obviously it is something which clobbers a buildworld, so maybe disk access or something like that (I have enough real memory that my system never pages). That's why I was wondering if there were some other benchmarks we could run. The only thing that I really do with my freebsd/sparc machine is buildworld's of freebsd/sparc, so there is nothing else where I would notice a major slowdown (even if it were occurring). On build #3 I noticed that 'top' constantly reported the CPU was 0.0% idle. Unfortunately I couldn't check that for build #4, because I didn't have a 'top' which matched the running kernel... -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu