From: Randy Hron <rwhron@earthlink.net>
To: Ed Sweetman <ed.sweetman@wmich.edu>
Cc: Andrew Morton <akpm@zip.com.au>,
linux-kernel@vger.kernel.org, marcelo@conectiva.com.br
Subject: Re: Linux 2.4.19-pre5
Date: Sun, 31 Mar 2002 07:42:15 -0500 [thread overview]
Message-ID: <E16reZK-0001IL-00@pintail.mail.pas.earthlink.net> (raw)
In-Reply-To: <20020330135333.A16794@rushmore> <E16rRCX-00068U-00@avocet.prod.itd.earthlink.net> <1017532120.641.75.camel@psuedomode>
> In this test I wanted to see this lag.
Just to be clear on what the "max latency" number is, it's the I/O
request within tiobench that waited the longest. I.E. The process notes
the time before it's ready to make the request, then notes the time
after the request is fullfilled. With a 2048MB file and a 4096 byte
block, there may be over 500,000 requests.
It's a relatively small number of requests that have the big latency
wait, so depending on the I/O requests your other applications make
during the test, a long wait may not be obvious, unless one or your
I/O's gets left at the end of the queue for a long time.
This is sometimes referred to as a "corner case".
The point where the "# of threads" manifests the "big latency
wall" is to note a dramatic change in longest I/O latency. This
point varies between the kernel trees.
The "big latency phenomenon" has been in the 2.4 tree at least
since 2.4.17 which is the first kernel I have this measurement
for. It probably goes back much further.
read_latency2
-------------
I tested read_latency2 with 2.4.19-pre5. pre5 vanilla hits
a wall at 32 tiobench threads for sequential reads. With
read_latency2, the wall is around 128.
For random reads, pre5 hits a wall at 64 threads. With
read_latency2, the wall is not apparent even with 128 threads.
read_latency2 appears to reduce sequential write latency
too, but not as dramatically as in the read tests.
next prev parent reply other threads:[~2002-03-31 12:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-30 18:53 rwhron
2002-03-30 19:49 ` Andrew Morton
2002-03-30 21:33 ` Randy Hron
2002-03-30 21:42 ` Ed Sweetman
2002-03-30 22:25 ` Randy Hron
2002-03-30 23:48 ` Ed Sweetman
2002-03-31 12:42 ` Randy Hron [this message]
2002-03-31 20:05 ` Ed Sweetman
2002-03-31 23:11 ` Randy Hron
2002-03-31 6:52 ` Andrew Morton
2002-04-01 0:36 ` Andrea Arcangeli
2002-04-01 1:24 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2002-04-04 9:08 Tom Holroyd
2002-04-04 19:28 ` Marcelo Tosatti
2002-04-05 4:13 ` Tom Holroyd
2002-04-16 14:49 ` Andrea Arcangeli
2002-04-17 1:22 ` Tom Holroyd
2002-03-29 21:47 Marcelo Tosatti
2002-03-30 20:40 ` Michal Jaegermann
2002-03-30 23:34 ` Keith Owens
2002-03-31 1:41 ` Michal Jaegermann
2002-04-04 19:50 ` Adrian Bunk
2002-04-04 21:41 ` Marcelo Tosatti
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=E16reZK-0001IL-00@pintail.mail.pas.earthlink.net \
--to=rwhron@earthlink.net \
--cc=akpm@zip.com.au \
--cc=ed.sweetman@wmich.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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
all inboxes | Powered by JetHome®