From: Sonny Rao <sonny@burdell.org>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: pbadari@us.ibm.com, Andreas Dilger <adilger@clusterfs.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: ext3 writepages ?
Date: Thu, 10 Feb 2005 15:25:34 -0500 [thread overview]
Message-ID: <20050210202534.GA3392@kevlar.burdell.org> (raw)
In-Reply-To: <OFE1E4ABD6.EF6C9753-ON88256FA4.006B0187-88256FA4.007098C6@us.ibm.com>
On Thu, Feb 10, 2005 at 12:30:23PM -0800, Bryan Henderson wrote:
> >Its possible that by doing larger
> >IOs we save CPU and use that CPU to push more data ?
>
> This is absolutely right; my mistake -- the relevant number is CPU seconds
> per megabyte moved, not CPU seconds per elapsed second.
> But I don't think we're close enough to 100% CPU utilization that this
> explains much.
>
> In fact, the curious thing here is that neither the disk nor the CPU seems
> to be a bottleneck in the slow case. Maybe there's some serialization I'm
> not seeing that makes less parallelism between I/O and execution. Is this
> a single thread doing writes and syncs to a single file?
>From what I've seen, without writepages, the application thread itself
tends to do the writing by falling into balance_dirty_pages() during
it's write call, while in the writepages case, a pdflush thread seems
to do more of the writeback. This also depends somewhat on
processor speed (and number) and amount of RAM.
To try and isolate this more, I've limited RAM (1GB) and number of
CPUs (1) on my testing setup.
So yes, there could be better parallelism in the writepages case, but
again this behavior could be a symptom and not a cause, but I'm not
sure how to figure that out, any suggestions ?
Sonny
next prev parent reply other threads:[~2005-02-10 20:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 15:32 ext3 writepages ? Badari Pulavarty
2005-02-02 20:19 ` Sonny Rao
2005-02-03 15:51 ` Badari Pulavarty
2005-02-03 17:00 ` Sonny Rao
2005-02-03 16:56 ` Badari Pulavarty
2005-02-03 17:24 ` Sonny Rao
2005-02-03 20:50 ` Sonny Rao
2005-02-08 1:33 ` Andreas Dilger
2005-02-08 5:38 ` Sonny Rao
2005-02-09 21:11 ` Sonny Rao
2005-02-09 22:29 ` Badari Pulavarty
2005-02-10 2:05 ` Bryan Henderson
2005-02-10 2:45 ` Sonny Rao
2005-02-10 17:51 ` Bryan Henderson
2005-02-10 19:02 ` Sonny Rao
2005-02-10 16:02 ` Badari Pulavarty
2005-02-10 18:00 ` Bryan Henderson
2005-02-10 18:32 ` Badari Pulavarty
2005-02-10 20:30 ` Bryan Henderson
2005-02-10 20:25 ` Sonny Rao [this message]
2005-02-11 0:20 ` Bryan Henderson
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=20050210202534.GA3392@kevlar.burdell.org \
--to=sonny@burdell.org \
--cc=adilger@clusterfs.com \
--cc=hbryan@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=pbadari@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).