From: Mike Galbraith <efault@gmx.de>
To: Thomas Pilarski <thomas.pi@arcor.de>
Cc: Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 12309] Large I/O operations result in slow performance and high iowait times
Date: Mon, 02 Nov 2009 16:56:04 +0100 [thread overview]
Message-ID: <1257177364.10173.23.camel@marge.simson.net> (raw)
In-Reply-To: <20091101134207.b97e4f5f.akpm@linux-foundation.org>
> --- Comment #412 from Thomas Pilarski <thomas.pi@arcor.de> 2009-11-01 21:28:24 ---
> Created an attachment (id=23618)
> --> (http://bugzilla.kernel.org/attachment.cgi?id=23618)
> Simple sleeper test case
>
> As this bug occurs more permanent while working in an virtual machine or while
> using java and I still think, that's this is a process scheduler bug (or
> something related). Here another test case, which shows the suspected
> behaviour. As there are many system calls while using a virtual machine, I have
> tries to find an equal test. The test case just sleeps for 1__s and measures the
> time difference of the usleep operation. I am using such many of the usleep
> operations, as the problems does not occur deterministic and I tried to catch
> as many as possibly occurrences.
>
> I have run this test case on three machines. The first one was a Core2 Duo with
> a first generation SDD (OCZ Core Series) with a poor write performance and on a
> Ubuntu kernel 2.6.31-14-generic. The partitions are block aligned. I have run
> this test, while my wife was using firefox. Every time, she was submitting
> something and firefox is using sqlite for writing the history, there was a high
> latency for the sleep test.
>
> Timediff 7629094: 16.80ms Total: 61.12ms
> Timediff 7629100: 18.82ms Total: 93.68ms
> Timediff 7629101: 19.96ms Total: 113.54ms
> Timediff 7629102: 19.98ms Total: 133.43ms
> Timediff 7629103: 19.97ms Total: 153.31ms
> Timediff 7629104: 20.00ms Total: 173.24ms
> Timediff 7629105: 19.96ms Total: 193.09ms
> Timediff 7629106: 20.02ms Total: 213.02ms
> Timediff 7629107: 19.94ms Total: 232.86ms
> Timediff 7636162: 16.40ms Total: 34.44ms
> Timediff 7636164: 19.90ms Total: 64.00ms
>
> While the duration of 100 usleep should be somewhere between 10ms and 20ms, 10
> usleep(1) takes more than 200ms. This behaviour is reproducible.
Can you please try the latest -rc? I spent the day trying to coax a
latency spike out of -tip, including thumping disk with dd, mysql+oltp
rw test et al, and failed.
-Mike
next parent reply other threads:[~2009-11-02 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091101134207.b97e4f5f.akpm@linux-foundation.org>
2009-11-02 15:56 ` Mike Galbraith [this message]
2009-11-02 20:26 ` Thomas Pilarski
2009-11-03 9:47 ` Mike Galbraith
[not found] <bug-12309-14043@http.bugzilla.kernel.org/>
[not found] ` <201003162357.o2GNvkNF024562@demeter.kernel.org>
2010-03-30 7:44 ` Thomas Pilarski
2010-03-31 0:25 ` Henrique de Moraes Holschuh
2010-04-03 19:19 ` Thomas Pilarski
2010-04-04 2:08 ` Henrique de Moraes Holschuh
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=1257177364.10173.23.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=thomas.pi@arcor.de \
/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®