From: Sean McCauliff <Sean.D.McCauliff@nasa.gov>
To: Andi Kleen <andi@firstfloor.org>
Cc: "Ted Ts'o" <tytso@mit.edu>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: High CPU Utilization When Copying to Ext4
Date: Fri, 8 Jul 2011 10:41:13 -0700 [thread overview]
Message-ID: <4E174139.4070501@nasa.gov> (raw)
In-Reply-To: <m27h7sd742.fsf@firstfloor.org>
43% of the destination file system is in use.
Sean
On 07/08/2011 10:17 AM, Andi Kleen wrote:
> Sean McCauliff<Sean.D.McCauliff@nasa.gov> writes:
>
>> I tried running perf on the copy program on subset of the sparse
>> files. It seems like ext4 is the source of high cpu utilization. At
>> this point this high cpu utilization is very annoying, but I can live
>> with this problem. If you know something simple I could do to
>> alleviate this problem I would be most appreciative. At the end of
>> this email is a consolidation of information about this problem.
>>
>> Events: 6M cycles
>> -76.80% java [kernel.kallsyms] [k] ext4_mb_good_group
>> - ext4_mb_good_group
>
> Is your file system too full?
>
> A lot of file system get inefficient in allocating blocks when the
> file system is nearly full.
>
> -Andi
>
next prev parent reply other threads:[~2011-07-08 17:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <341DAA96EE3A8444B6E4657BE8A846EA4B3DA126FE@NDJSSCC06.ndc.nasa.gov>
2011-06-27 3:05 ` High CPU Utilization When Copying to Ext4 Ted Ts'o
2011-06-27 9:24 ` Lukas Czerner
2011-06-28 18:37 ` Mccauliff, Sean D. (ARC-PX)[Lockheed Martin Space OPNS]
2011-06-28 20:14 ` Theodore Tso
2011-06-28 20:20 ` Mccauliff, Sean D. (ARC-PX)[Lockheed Martin Space OPNS]
2011-06-29 13:08 ` Theodore Tso
2011-06-30 0:01 ` Sean McCauliff
2011-06-30 2:33 ` Ted Ts'o
2011-07-08 17:08 ` Sean McCauliff
2011-07-08 17:17 ` Andi Kleen
2011-07-08 17:41 ` Sean McCauliff [this message]
2011-07-08 18:24 ` Ted Ts'o
2011-06-28 20:17 ` Andreas Dilger
2011-06-29 23:16 ` Sean McCauliff
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=4E174139.4070501@nasa.gov \
--to=sean.d.mccauliff@nasa.gov \
--cc=andi@firstfloor.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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.