From owner-freebsd-alpha@FreeBSD.ORG Tue Mar 8 15:50:37 2005 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25BF116A4CE for ; Tue, 8 Mar 2005 15:50:37 +0000 (GMT) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA60143D46 for ; Tue, 8 Mar 2005 15:50:36 +0000 (GMT) (envelope-from kirk@strauser.com) Received: from localhost (localhost [127.0.0.1]) by kanga.honeypot.net (Postfix) with ESMTP id E681222085B for ; Tue, 8 Mar 2005 09:50:35 -0600 (CST) Received: from kanga.honeypot.net ([127.0.0.1]) by localhost (kanga.honeypot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 42061-12 for ; Tue, 8 Mar 2005 09:50:27 -0600 (CST) Received: from janus.daycos.com (janus.daycos.com [204.26.70.77]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by kanga.honeypot.net (Postfix) with ESMTP id 5730021C87E for ; Tue, 8 Mar 2005 09:50:27 -0600 (CST) From: Kirk Strauser To: freebsd-alpha@freebsd.org Date: Tue, 8 Mar 2005 09:50:23 -0600 User-Agent: KMail/1.7.2 References: <200503072107.13313.kirk@strauser.com> <20050308034852.GX22167@cicely12.cicely.de> In-Reply-To: <20050308034852.GX22167@cicely12.cicely.de> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1326056.fzWiklBpgM"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200503080950.26844.kirk@strauser.com> X-Virus-Scanned: amavisd-new at honeypot.net Subject: Re: Question about cc flags in buildkernel X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2005 15:50:37 -0000 --nextPart1326056.fzWiklBpgM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 07 March 2005 21:48, Bernd Walter wrote: > There is no speed influence by this option.=20 Thanks for the explanation. I wasn't sure, and it was nice to get a bit of= =20 confirmation. > How did you compare speed? It's more of a general observation: everything is just slow, slow, slow. =20 =46or example, loading the man page for 'zshall' (from the shells/zsh port)= =20 takes most of a minute: # time man zshall > /dev/null Formatting page, please wait...Done. man zshall > /dev/null 47.39s user 0.99s system 93% cpu 51.523 total during which troff and grotty are using 100% of the CPU. SSH connections t= o=20 it take a long time to start: $ time ssh gopher exit ssh gopher exit 0.04s user 0.03s system 0% cpu 7.675 total If I run that with "-v", I can see that it spends most of that time in=20 "Entering interactive session." The hard drive isn't completely horrible=20 (~8MB sustained transfers at less than 8% CPU usage), and it has 3 fxp NICs= =20 that barely register under heavy network load. I installed 256MB of RAM=20 (with 2MB of L2 cache, I think), and it's currently only 12KB into swap. =20 In other words, by every metric I can think of, it appears the bottleneck=20 is that the CPU is dog slow. > If it's just from compile time, you shouldn't forget that gcc-3 is much > slower than the older gcc and that compiling for alpha is a much harder > job than compiling for i386. Compile times don't really bother me; I launch big jobs and then walk away= =20 from it until they're done. That's also why I was using the higher-order=20 optimization flags. They make the compiles quite a bit slower, but the=20 results usually seem to be worth it (which here means "less painful"). I'm really not expecting miracles from this little machine, but my K6/333=20 laptop with less RAM and a 2.5" IDE harddrive smokes it in every way. I=20 was sort of hoping I'd found the "aha!" detail that would account for the=20 awful performance. =2D-=20 Kirk Strauser --nextPart1326056.fzWiklBpgM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iD8DBQBCLcnC5sRg+Y0CpvERApQLAJwO8E6tIRBDIy+9Vi2WH95vpmp6ZwCgmvU4 i6m4lHkqmCnToWsrEyvVw0s= =eH9P -----END PGP SIGNATURE----- --nextPart1326056.fzWiklBpgM--