From: Matthew Wilcox <willy@debian.org>
To: Peter Lavender <plaven@bigpond.net.au>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] performance?
Date: Tue, 26 Mar 2002 15:44:44 +0000 [thread overview]
Message-ID: <20020326154444.D26865@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20020326224358.B28171@piglet>; from plaven@bigpond.net.au on Tue, Mar 26, 2002 at 10:43:58PM +1100
On Tue, Mar 26, 2002 at 10:43:58PM +1100, Peter Lavender wrote:
> It wasn't until I compiled it on my p90 with 48 meg ram running a a
> zillion services and daemons that I noticed just how slow the 715 is.
> Running the program proved this even further.
Would you mind posting some numbers?
Also, let's try to figure out what other variables are a factor. Can you
compare gcc-3.0 on your x86 to the current compiler?
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2002-03-26 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-26 11:43 [parisc-linux] performance? Peter Lavender
2002-03-26 15:44 ` Matthew Wilcox [this message]
2002-03-27 7:06 ` Peter Lavender
2002-03-27 12:00 ` Rafael E. Herrera
2002-03-28 5:06 ` Carlos O'Donell Jr.
2002-03-28 6:10 ` Peter Lavender
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020326154444.D26865@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=parisc-linux@parisc-linux.org \
--cc=plaven@bigpond.net.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox