From: Thomas Fjellstrom <thomas@fjellstrom.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: rsync causing high loads on 2.6.36-rc4
Date: Tue, 21 Sep 2010 19:18:02 -0600 [thread overview]
Message-ID: <201009211918.02364.thomas@fjellstrom.ca> (raw)
In-Reply-To: <201009211859.05770.thomas@fjellstrom.ca>
On September 21, 2010, Thomas Fjellstrom wrote:
> This isn't something I remember happening with older kernels, but I just
> started an rsync from an nfs share over GbE, to a external SATA drive over
> usb 2, and I'm seeing both of my laptop's cores hitting 80-100% cpu use,
> two rsync processes are using 20-40% each, some kworker's are using tiny
> bits (2-10%), and kswapd0 is hovering around 5%. Quite a lot of the time
> seems to be io- wait. load average is almost at 6.
>
> This is a dual core T9400 core2duo laptop, with 4GB ram, running full amd64
> (64bit 2.6.36-rc4 kernel and userspace).
>
> Its impacting desktop interactivity quite a lot.
It's not quite as bad with a regular cp, but it does affect my laptop in the
same way.
--
Thomas Fjellstrom
thomas@fjellstrom.ca
prev parent reply other threads:[~2010-09-22 1:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 0:59 Thomas Fjellstrom
2010-09-22 1:18 ` Thomas Fjellstrom [this message]
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=201009211918.02364.thomas@fjellstrom.ca \
--to=thomas@fjellstrom.ca \
--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
Powered by JetHome