From: Robert Hancock <hancockrwd@gmail.com>
To: Satish Eerpini <eerpini@gmail.com>
Cc: Mark Knecht <markknecht@gmail.com>,
Rik van Riel <riel@redhat.com>, Ray Lee <ray-lk@madrabbit.org>,
Christoph Lameter <cl@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: unresponsiveness on linux desktop during file copy
Date: Sun, 17 May 2009 02:54:05 -0600 [thread overview]
Message-ID: <4A0FD0AD.4030402@gmail.com> (raw)
In-Reply-To: <93655eb70905152352n6f82ef9dubb9b36e5be161ac7@mail.gmail.com>
Satish Eerpini wrote:
>> Do you believe this was working better on an earlier kernel? If so you
>> might drop back and see if these commands work better. If so that
>> would suggest a regression of some type.
>
> I remember good performance with 2.6.26.x series, ... but I could not
> try that out, ,... things on a 2.6.27.23 kernel seem no better :
>
> Linux 2.6.27.23 (satish) 05/16/2009
>
> 12:11:18 PM CPU %user %nice %system %iowait %steal %idle
> 12:11:21 PM all 0.00 0.00 3.92 75.65 0.00 20.42
> 12:11:24 PM all 0.00 0.00 3.55 67.85 0.00 28.59
> 12:11:27 PM all 0.16 0.00 4.51 45.09 0.00 50.24
> 12:11:30 PM all 0.00 0.00 3.59 44.77 0.00 51.63
> 12:11:33 PM all 0.16 0.00 5.25 82.51 0.00 12.08
> Average: all 0.06 0.00 4.17 63.24 0.00 32.53
>
> the average disk speed was about 10.5 MB/s, indeed the average IOWAIT
> is more than that in the latest kernel, I will see if I can test it on
> a 2.6.26.x kernel or earlier one and send you guys the stats.
High iowait during a file copy with no other activity is entirely
normal. If you have a core that has nothing to do but wait for IO to
complete, you'll get iowait time. This isn't indicating a problem.
next prev parent reply other threads:[~2009-05-17 8:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 17:07 unresponsiveness on linux desktop during file copy Satish Eerpini
2009-05-15 17:12 ` Mark Knecht
[not found] ` <93655eb70905151024o634f8432j6c3db85df1f6ddfc@mail.gmail.com>
[not found] ` <5bdc1c8b0905151120p5aa58318t1765544fbbb695b2@mail.gmail.com>
2009-05-16 2:38 ` Satish Eerpini
2009-05-16 2:47 ` Mark Knecht
2009-05-16 3:12 ` Satish Eerpini
2009-05-16 3:37 ` Mark Knecht
2009-05-16 6:52 ` Satish Eerpini
2009-05-16 21:11 ` Mark Knecht
2009-05-17 8:54 ` Robert Hancock [this message]
2009-05-17 9:04 ` Satish Eerpini
2009-05-17 8:52 ` Robert Hancock
2009-05-15 18:02 ` Ray Lee
2009-05-15 19:33 ` Christoph Lameter
2009-05-16 16:03 ` Ray Lee
2009-05-16 17:38 ` Rik van Riel
2009-05-17 1:19 ` Wu Fengguang
2009-05-17 1:27 ` Satish Eerpini
2009-05-17 2:08 ` Wu Fengguang
2009-05-17 4:30 ` Satish Eerpini
2009-05-17 4:57 ` Arjan van de Ven
2009-05-17 4:58 ` Wu Fengguang
2009-05-17 6:18 ` Satish Eerpini
2009-05-17 9:30 ` Wu Fengguang
2009-05-17 12:01 ` Satish Eerpini
2009-05-17 12:17 ` Wu Fengguang
2009-05-17 12:27 ` Satish Eerpini
2009-05-17 12:39 ` Wu Fengguang
2009-05-17 13:03 ` Satish Eerpini
2009-05-17 13:11 ` Wu Fengguang
2009-05-17 13:43 ` Satish Eerpini
2009-05-17 13:14 ` Michael S. Zick
2009-05-16 2:28 ` Satish Eerpini
2009-05-16 14:25 ` Satish Eerpini
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=4A0FD0AD.4030402@gmail.com \
--to=hancockrwd@gmail.com \
--cc=cl@linux-foundation.org \
--cc=eerpini@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markknecht@gmail.com \
--cc=ray-lk@madrabbit.org \
--cc=riel@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.