public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
	Aaron Lehmann <aaronl@vitelus.com>,
	linux-kernel@vger.kernel.org
Subject: Re: ext3 throughput woes on certain (possibly heavily fragmented) files
Date: Fri, 6 Sep 2002 18:24:57 +0100	[thread overview]
Message-ID: <20020906182457.F3029@redhat.com> (raw)
In-Reply-To: <15736.57972.202889.872554@laputa.namesys.com>; from Nikita@Namesys.COM on Fri, Sep 06, 2002 at 09:14:28PM +0400

Hi,

On Fri, Sep 06, 2002 at 09:14:28PM +0400, Nikita Danilov wrote:

> Another possible solution is to try to "defer" allocation. For example,
> in reiser4 (and XFS, I believe) extents are allocated on the transaction
> commit and as a result, if file was created by several writes, it will
> still be allocated as one extent.

Ext2 has a preallocation mechanism so that if you have multiple
writes, they get dealt with to some extent as a single allocation.
However, that doesn't work over close(): the preallocated blocks are
discarded wheneven we close the file.

The problem with mail files, though, is that they tend to grow quite
slowly, so the writes span very many transactions and we don't have
that opportunity for coalescing the writes.  Actively defragmenting on
writes is an alternative in that case.

Cheers,
 Stephen

  parent reply	other threads:[~2002-09-06 17:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-03  9:24 ext3 throughput woes on certain (possibly heavily fragmented) files Aaron Lehmann
2002-09-06 16:06 ` Stephen C. Tweedie
2002-09-06 17:14   ` Nikita Danilov
2002-09-06 17:22     ` Hans Reiser
2002-09-06 21:02       ` Aaron Lehmann
2002-09-06 22:05         ` Hans Reiser
2002-09-06 17:24     ` Stephen C. Tweedie [this message]
2002-09-16 22:39       ` Simon Kirby
2002-09-17 16:53         ` Andreas Dilger
2002-09-17 21:55         ` jw schultz
  -- strict thread matches above, loose matches on Subject: below --
2002-09-16 18:00 Peter Niemayer

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=20020906182457.F3029@redhat.com \
    --to=sct@redhat.com \
    --cc=Nikita@Namesys.COM \
    --cc=aaronl@vitelus.com \
    --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