From: Tom Sightler <ttsig@tuxyturvy.com>
To: "Gord R. Lamb" <glamb@lcis.dyndns.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Samba performance / zero-copy network I/O
Date: Wed, 14 Feb 2001 17:40:31 -0500 (EST) [thread overview]
Message-ID: <982190431.3a8b095f4b3c4@eargle.com> (raw)
In-Reply-To: <Pine.LNX.4.32.0102141548440.27843-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.32.0102141548440.27843-100000@localhost.localdomain>
Quoting "Gord R. Lamb" <glamb@lcis.dyndns.org>:
> On Wed, 14 Feb 2001, Jeremy Jackson wrote:
>
> > "Gord R. Lamb" wrote:
> > > in etherchannel bond, running
> linux-2.4.1+smptimers+zero-copy+lowlatency)
Not related to network, but why would you have lowlatency patches on this box?
My testing showed that the lowlatency patches abosolutely destroy a system
thoughput under heavy disk IO. Sure, the box stays nice and responsive, but
something has to give. On a file server I'll trade console responsivness for IO
performance any day (might choose the opposite on my laptop).
My testing wasn't very complete, but heavy dbench and multiple simultaneous file
copies both showed significantly lower performance with lowlatency enabled, and
returned to normal when disabled.
Of course you may have had lowlatency disabled via sysctl but I was mainly
curious if your results were different.
Later,
Tom
next prev parent reply other threads:[~2001-02-14 22:40 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 [this message]
2001-02-16 2:24 ` Gord R. Lamb
2001-02-16 14:51 ` Andrew Morton
2001-02-16 20:49 ` Tom Sightler
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=982190431.3a8b095f4b3c4@eargle.com \
--to=ttsig@tuxyturvy.com \
--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