From: Andrew Morton <akpm@zip.com.au>
To: J Sloan <jjs@lexus.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Testing the effects of the low latency patch
Date: Thu, 24 Jan 2002 17:03:29 -0800 [thread overview]
Message-ID: <3C50AEE1.2300BB05@zip.com.au> (raw)
In-Reply-To: <3C50AC22.7090203@lexus.com>
J Sloan wrote:
>
> I had earlier posted reports about the low latency patch in terms
> that are too subjective - e.g. saying that "quake 3 arena feels much
> smoother and I frag a lot more" isn't the kind of hard statistical
> evidence demanded by some. I have attempted to quanitify the latency
> differences in one of the workloads where I see and feel a difference.
mm. Numbers. Nice.
>
> 2.4.18-pre6+tux+nfs-fixes
> -------------
> ...
> 7.6 1
> 7.8 1
> 21.1 1
This is the stock kernel. In twenty minutes you suffered
precisely *one* scheduling overrun which is perceptible
by a human. The rest are much shorter than your monitor's
refresh interval. Interesting, yes?
These results are better than the ones I normally measure.
> ...
> The dbench results:
>
> 2.4.18-pre6+tux+nfs-fixes
> ---------------------------------
> ...
> Throughput 48.9432 MB/sec (NB=61.179 MB/sec 489.432 MBit/sec) 16 procs
> ...
>
> 2.4.18-pre6+tux+nfs-fixes + low latency patch
> ---------------------------------
> ...
> Throughput 106.361 MB/sec (NB=132.951 MB/sec 1063.61 MBit/sec) 16 procs
> ...
Now that's odd.
-
next prev parent reply other threads:[~2002-01-25 1:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 0:51 Testing the effects of the low latency patch J Sloan
2002-01-25 1:03 ` Andrew Morton [this message]
2002-01-25 1:14 ` J Sloan
2002-01-25 1:23 ` Andrew Morton
2002-01-25 1:37 ` J Sloan
2002-01-25 1:19 ` J Sloan
2002-01-25 1:39 ` Mark Hahn
2002-01-25 2:26 ` J Sloan
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=3C50AEE1.2300BB05@zip.com.au \
--to=akpm@zip.com.au \
--cc=jjs@lexus.com \
--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