From: Alex deVries <adevries@linuxcare.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] performance
Date: Wed, 27 Dec 2000 13:53:46 -0500 [thread overview]
Message-ID: <3A4A3ABA.4EC6D5A7@linuxcare.com> (raw)
In-Reply-To: E14BL04-0002Zj-00@the-village.bc.nu
Alan Cox wrote:
> > http://www.spec.org/osg/web99/results/res2000q4/
> >
> > This shows some PA-RISC machines running HPUX performing reasonably
> > well.
>
> Specweb is basically a con. Its not a materially valuable benchmark. It benches
> how fast your irq handler path is, how fast your memory cache is, how good
> your DMA transfers are. It has almost nothing to do with how good a web
> server the box is.
I agree that specweb might not actually be functionally practical.
This might not be the case with specweb, but sometimes specifications do
have the ability to influence customers regardless of their validity.
That's interesting for one reason: if the marketing helps make potential
customers think that parisc-linux is fast, they'll buy parisc boxes, and
HP is more likely to allocate developer time on this project.
- Alex
--
Alex deVries, Principal Solutions Architect, The Puffins at Linuxcare
613.562.2759 tel
alex@linuxcare.com, http://www.linuxcare.com/
Linuxcare, Support for the revolution.
next prev parent reply other threads:[~2000-12-27 18:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 17:05 [parisc-linux] performance Alex deVries
2000-12-27 17:52 ` Grant Grundler
2000-12-27 18:08 ` Alan Cox
2000-12-27 18:53 ` Alex deVries [this message]
2000-12-30 6:13 ` Grant Grundler
2000-12-30 16:50 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2000-03-01 5:50 [parisc-linux] Performance T. Martin
2000-03-01 14:18 ` Michael Shalayeff
2000-03-02 3:54 ` Steve Shack
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=3A4A3ABA.4EC6D5A7@linuxcare.com \
--to=adevries@linuxcare.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=parisc-linux@thepuffingroup.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.