public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Tom Sightler" <ttsig@tuxyturvy.com>
To: "Andrew Morton" <andrewm@uow.edu.au>
Cc: "Gord R. Lamb" <glamb@lcis.dyndns.org>, <linux-kernel@vger.kernel.org>
Subject: Re: Samba performance / zero-copy network I/O
Date: Fri, 16 Feb 2001 15:49:35 -0500	[thread overview]
Message-ID: <001f01c09859$f928dd10$25040a0a@zeusinc.com> (raw)
In-Reply-To: <Pine.LNX.4.32.0102141548440.27843-100000@localhost.localdomain>,	<Pine.LNX.4.32.0102141548440.27843-100000@localhost.localdomain> <982190431.3a8b095f4b3c4@eargle.com> <3A8D3E62.98F5AD6A@uow.edu.au>

> > My testing showed that the lowlatency patches abosolutely destroy a
system
> > thoughput under heavy disk IO.
>
> I'm surprised - I've been keeping an eye on that.
>
> Here's the result of a bunch of back-to-back `dbench 12' runs
> on UP, alternating with and without LL:

It's interesting that your results seem to show an improvement in
performance, while mine show a consistent drop.  My tests were not very
scientific, and I was running much higher dbench processes, 'dbench 64' or
'dbench 128', and at those levels performance with lowlatency enabled fell
though the floor on my setup.

My system is a PIII 700Mhz, Adaptec 7892 Ultra-160, software RAID1,
reiserfs, 256MB RAM.

Under lower loads, like the 'dbench 12' lowlatency only showed only a few
percent loss, but once you approached the levels around 50 things really
went downhill.

I might try to do a more complete test, maybe there's something else in my
config that would make this be a problem, but it was definately quite
noticable.

Later,
Tom



  reply	other threads:[~2001-02-16 20:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-14 20:14 Samba performance / zero-copy network I/O Gord R. Lamb
2001-02-14 20:29 ` Alan Cox
2001-02-14 20:42 ` Jeremy Jackson
2001-02-14 20:53   ` Gord R. Lamb
2001-02-14 22:40     ` Tom Sightler
2001-02-16  2:24       ` Gord R. Lamb
2001-02-16 14:51       ` Andrew Morton
2001-02-16 20:49         ` Tom Sightler [this message]
2001-02-17  8:17     ` Anton Blanchard
2001-02-19 16:47       ` Gord R. Lamb

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='001f01c09859$f928dd10$25040a0a@zeusinc.com' \
    --to=ttsig@tuxyturvy.com \
    --cc=andrewm@uow.edu.au \
    --cc=glamb@lcis.dyndns.org \
    --cc=linux-kernel@vger.kernel.org \
    /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