All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Masover <ninja@slaphack.com>
To: Quinn Harris <lists@qutek.net>
Cc: reiserfs-list@namesys.com
Subject: Re: Relocating files for faster boot/start-up on reiser(fs/4)
Date: Thu, 14 Sep 2006 17:23:25 -0500	[thread overview]
Message-ID: <4509D65D.7040908@slaphack.com> (raw)
In-Reply-To: <200609141609.06713.lists@qutek.net>

Quinn Harris wrote:
> On Thursday 14 September 2006 13:55, David Masover wrote:
>> Quinn Harris wrote:
>>> The boot optimization was over 3885 files.  Ideally those files would be
>>> ordered head to tail in a sequence that perfectly matches the order they
>>> will be read.
>>>
>>> I bring this up here because I expect with reiser4, a repacker, and this
>> Now that you mention it, do you have a control of some sort to prove
>> this isn't just fragmentation?  That is, copy the files you're messing
>> with in some random order (that should make booting slower), and
>> benchmark that?
> 
> That is a good point.  Recording the disk layout before and after to compare 
> relative fragmentation would be a good idea.  As well as randomizing the 
> sequence as a sanity check.
> 
> Also note that during boot I was using readahead on all 3885 files.  So the 
> kernel has a good opportunity to rearrange the reads.  And the read sequence 
> doesn't necessary match the order its needed (though I tried to get that).

Speaking of which, did you parallize the boot process at all?  I'd 
estimate my system easily spent more than 50% of its boot time not 
touching the disk at all before I did that.  Gentoo can do this, I'm not 
sure what else, as it kind of needs your init system to understand 
dependencies.

As far as faster load times for Firefox and OpenOffice, you may be on to 
something here, but then, these apps probably match up pretty well with 
the on-disk format, too.

This would probably be most useful for a case where you have to read a 
lot of small files, with relatively low CPU usage, in a fairly 
unpredictable order.  I suspect it would be nice for Gentoo's Portage 
tree, though I can't think what else.

  reply	other threads:[~2006-09-14 22:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13 20:51 Relocating files for faster boot/start-up on reiser(fs/4) Quinn Harris
2006-09-13 21:10 ` Peter
2006-09-14  3:10   ` Quinn Harris
2006-09-14 19:55     ` David Masover
2006-09-14 22:09       ` Quinn Harris
2006-09-14 22:23         ` David Masover [this message]
2006-09-15  5:15           ` Toby Thain
2006-09-15 21:20             ` Quinn Harris
2006-09-15 22:27               ` David Masover
2006-09-16  0:01                 ` Quinn Harris
2006-09-16  8:59                   ` David Masover
2006-09-18  9:36               ` PFC
2006-09-18 22:32                 ` Quinn Harris
2006-09-14 14:01   ` cmaurand

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=4509D65D.7040908@slaphack.com \
    --to=ninja@slaphack.com \
    --cc=lists@qutek.net \
    --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.