All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lutz Vieweg <lkv@isg.de>
To: reiserfs-list@namesys.com
Subject: Fragmentation / repacker / append-performance
Date: Fri, 18 Nov 2005 17:34:49 +0100	[thread overview]
Message-ID: <437E02A9.2050107@isg.de> (raw)

Hans Reiser wrote:

 > 6% fragmentation is enormous.  You very much need the
 > repacker we have not yet written.....

There has been talk about such a feature for a long time -
did anybody already write a concept on how to do this?
Has an effort been estimated? Is somebody already assigned
to that task?

It's not too difficult for us to implement de-fragmentation
mechanisms on the application level, but if the file
system can do it - even better...

We're currently considering reiser4 for an application
that we know would suffer badly from fragmentation, as
it needs to often append small amounts of data (a few
bytes to a few kB) to lots of files (6M).

Alas, such a task does not seem to be covered by any
of the usual benchmarks, so we have to do measurements
on our own. Any suggestion for optimal configuration
parameters we should use?

As of yet, we are using XFS for this task, which is
significantly faster for that particular application
than reiser3. Alas, XFS/kernel-2.6/SMP is known to
be unstable under high load for almost a year now,
but since the problem is hard to reproduce and those
who only need a file server can live with using just
one CPU it does not seem to get fixed anytime soon.

Regards,

Lutz Vieweg

PS: I'm still glad we sponsored the 64bit-port years
     ago, as we're still using reiser3 on a lot of
     systems that can really use it - and of course
     newly bought systems are 64bit architectures... :-)


             reply	other threads:[~2005-11-18 16:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-18 16:34 Lutz Vieweg [this message]
2005-11-19  4:50 ` Fragmentation / repacker / append-performance michael chang

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=437E02A9.2050107@isg.de \
    --to=lkv@isg.de \
    --cc=reiserfs-list@namesys.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 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.