From: Chris Mason <chris.mason@oracle.com>
To: Piavlo <piavka@cs.bgu.ac.il>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: high cpu load for random write
Date: Wed, 1 Jul 2009 11:53:26 -0400 [thread overview]
Message-ID: <20090701155326.GC22821@think> (raw)
In-Reply-To: <4A4B1E9F.1070201@cs.bgu.ac.il>
On Wed, Jul 01, 2009 at 11:30:23AM +0300, Piavlo wrote:
> Hi Chris,
>
> I've tried a test with mount -o nodatacow and see no noticeable
> difference in cpu load.
>
> Results with -o nodatacow (dmesg confirms "btrfs: setting nodatacow")
> Tiotest results for 1 concurrent io threads:
Well, it turns out that I broke nodatacow when I merged Christoph's attr
patch. This high CPU usage during tiotest is all checksums.
The CPU times look like random writes are using much more CPU, but
really they are just doing much less IO (59MB vs 9000MB). This makes
the CPU percentage look much higher because the test overall isn't
waiting on IO much at all.
Here are my results for your tiotest run with a fixed nodatacow:
test results for 1 concurrent io threads:
,----------------------------------------------------------------------.
| Item | Time | Rate | Usr CPU | Sys CPU |
+-----------------------+----------+--------------+----------+---------+
| Write 9000 MBs | 87.6 s | 102.774 MB/s | 0.4 % | 11.4 % |
| Random Write 59 MBs | 40.7 s | 1.438 MB/s | 0.0 % | 0.3 % |
`----------------------------------------------------------------------'
I'll queue the fix up for Linus.
-chris
next prev parent reply other threads:[~2009-07-01 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 12:54 high cpu load for random write Piavlo
2009-06-30 13:41 ` Chris Mason
2009-07-01 8:30 ` Piavlo
2009-07-01 15:53 ` Chris Mason [this message]
2009-07-01 8:51 ` Piavlo
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=20090701155326.GC22821@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=piavka@cs.bgu.ac.il \
/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