[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1303408883-sup-1495@think>
Date: Thu, 21 Apr 2011 14:02:43 -0400
From: Chris Mason <chris.mason@...cle.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: Andreas Dilger <adilger@...ger.ca>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
linux-ext4 <linux-ext4@...r.kernel.org>, xfs <xfs@....sgi.com>,
jack <jack@...e.cz>, axboe <axboe@...nel.dk>,
dchinner <dchinner@...hat.com>
Subject: Re: buffered writeback torture program
Excerpts from Christoph Hellwig's message of 2011-04-21 14:02:13 -0400:
> On Thu, Apr 21, 2011 at 11:59:37AM -0600, Andreas Dilger wrote:
> > But doesn't XFS have potentially very large extents, especially in the case of files that were fallocate()'d or linearly written? If there is a single 8GB extent, and then random writes within that extent (seems very database like) grouping the all of the writes in the extent doesn't seem so great.
>
> It doesn't cluster any writes in an extent. It only writes out
> additional dirty pages directly following that one we were asked to
> write out. As soon as we hit a non-dirty page we give up.
For this program, they are almost all dirty pages.
I tried patching it to give up if we seek but it is still pretty slow.
There's something else going on in addition to the xfs clustering being
too aggressive.
I'll try dropping the clustering completley.
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists