All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Riccardi <fabio@chromium.com>
To: mingo@elte.hu
Cc: Zach Brown <zab@zabbo.net>,
	Linux Kernel List <linux-kernel@vger.kernel.org>,
	"David S. Miller" <davem@redhat.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: numbers?
Date: Fri, 20 Apr 2001 14:23:30 -0700	[thread overview]
Message-ID: <3AE0A8D2.3CD79B8D@chromium.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0104202033160.2706-100000@elte.hu>

Ingo Molnar wrote:

> > On a Dell PowerEdge 1550/1000 the published TUX 2 result is 2765.
> >
> > If you take into account the fact that the 1550 has a faster processor
> > (1GHz) and a more modern bus architecture (Serverworks HE with memory
> > interleaving and a triple PCI bus), the performance is roughly the
> > same.
>
> the system was IO-limited (given that a ~9 GB fileset was running on a 2
> GB RAM system), so CPU speed has not a big impact. I'd say it makes no
> sense to compare different systems.

>From what I've seen the major impact comes from the disk IO bandwidth to
memory size ratio and from the PCI bus to memory bandwidth.

I agree that comparing different hardware architectures is a tricky business,
but you asked me to comment on some of the comparisons that you made...

> > The static pages work fine, the dynamic module gets executed, but for
> > some reason it fails to open the postlog file and to spawn the spec
> > utility tasks at reset time.
>
> the newest TUX code chroots into docroot, so you should either use "/" as
> the docroot, or put /lib libraries into your docroot.

Oh, the docs don't mention anything of that... I'll try to set the docroot as
you say

> > I'll make an alpha release of X15 available for download by the end of
> > next week, so people will be able to test it independently.
>
> (will source code be available so we can see whether it's an apples to
> apples thing?)

I'll release the source for the SPEC dynamic code dll, which indeed is just a
straight porting of the TUX dynamic code from the SPEC site.

 - Fabio



  reply	other threads:[~2001-04-20 21:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-20  3:38 user space web server accelerator support Fabio Riccardi
2001-03-20  3:51 ` David S. Miller
2001-03-20  3:58   ` Fabio Riccardi
2001-03-20  3:59     ` David S. Miller
2001-03-20  4:07       ` Fabio Riccardi
2001-03-20 13:08         ` Erik Mouw
2001-03-20 16:01         ` Zach Brown
2001-03-23  3:53       ` Fabio Riccardi
2001-03-23 19:14         ` Zach Brown
2001-03-23 20:24           ` kernel support for _user space_ web server accelerator Fabio Riccardi
2001-04-18 16:19             ` numbers? Ingo Molnar
2001-04-20 19:35               ` numbers? Fabio Riccardi
2001-04-20 18:42                 ` numbers? Ingo Molnar
2001-04-20 21:23                   ` Fabio Riccardi [this message]
2001-04-21  3:42                     ` numbers? Ingo Molnar
2001-04-20 20:53                 ` numbers? Alan Cox
2001-04-20 21:12                   ` numbers? Fabio Riccardi

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=3AE0A8D2.3CD79B8D@chromium.com \
    --to=fabio@chromium.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=zab@zabbo.net \
    /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.