All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Masover <ninja@slaphack.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Ingo Bormuth <ibormuth@efil.de>, reiserfs-list@namesys.com
Subject: Re: some testing questions
Date: Tue, 15 Aug 2006 16:52:47 -0500	[thread overview]
Message-ID: <44E2422F.8090708@slaphack.com> (raw)
In-Reply-To: <44E228B7.10505@namesys.com>

Hans Reiser wrote:
> Ingo Bormuth wrote:
>>
>> #df:
>> /dev/hda8              6357768   3478716   2879052  55% /cache
>>  
>> Before doing so, the partition was >90% full. 
> The performance difference between >90% full and 55% full will be large
> on every filesystem.  When we ship a repacker, that will be less true,
> because we will have large chunks of unused space after the repacker runs.

Not always true.  For one, doesn't Reiser4 arbitrarily reserve 5%?  For 
another, look at his results -- unless I'm wrong, that's 3-7% 
fragmentation.  If I'm wrong, it's more like .03-.07%.

And lastly, at a certain point, percentages aren't really that accurate. 
  I've got a 350 or 400 gig partition which is 95% full, according to df 
(which if I was right about that 5%, it's more like 90% full) and that 
still leaves a solid 10-20 gigs free.

I mean, yes, performance will eventually start to suffer, but how much 
time and activity will it take to fragment 20 gigs of free space, 
especially with lazy allocation?

  reply	other threads:[~2006-08-15 21:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-11 17:44 some testing questions Gasper Azman
2006-08-14 12:15 ` Vladimir V. Saveliev
2006-08-15 14:21   ` Ingo Bormuth
2006-08-15 20:04     ` Hans Reiser
2006-08-15 21:52       ` David Masover [this message]
2006-08-15 22:03         ` Hans Reiser
  -- strict thread matches above, loose matches on Subject: below --
2006-08-14 14:07 Gasper Azman

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=44E2422F.8090708@slaphack.com \
    --to=ninja@slaphack.com \
    --cc=ibormuth@efil.de \
    --cc=reiser@namesys.com \
    --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.