From: Kai Krakow <hurikhan77+btrfs@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: exploit preload daemon to defragment most needed files
Date: Sun, 05 May 2013 18:21:45 +0200 [thread overview]
Message-ID: <khdi5a-sfp.ln1@hurikhan.ath.cx> (raw)
In-Reply-To: 20130505135708.GA24548@mother.pipebreaker.pl
Tomasz Torcz <tomek@pipebreaker.pl> schrieb:
>> Although this is about the preload daemon, my intended audience for this
>> matter is the btrfs community. So I'm posting this here.
>>
>> I've created a small script here[1] to read the preload daemon state file
>> and use this to run the btrfs defragmenter/compressor on these files. The
>> idea was to have some proof-of-concept to maybe integrate defragmentation
>> capabilities directly into preload.
>
> In similar spirit, systemd's readhead defrag files on btrfs. Here's the
> commit:
Yes! :-) Actually that is where I had my idea from. But preload takes on
(boot finished, preload user's enviroment) where readahead stops (readahead
files needed by daemons, until about 10s after last daemon loaded) working
with my files.
I think it is a great idea doing this kind of stuff in preloaders and
"readaheaders".
If I understood it right, systemd readahead does not only just defrag the
files, it relocates them into the order needed during boot. Actually, that
seems pretty effective, as my system (no SSD) finishes booting all daemons
within less than 10s (on mraid1/draid0 3 device btrfs, plain old harddisks,
no SSD). Just lightdm/kdm then take ages to load. Still need to figure out
why but that's another story.
Regards,
Kai
prev parent reply other threads:[~2013-05-05 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-05 9:42 exploit preload daemon to defragment most needed files Kai Krakow
2013-05-05 13:57 ` Tomasz Torcz
2013-05-05 16:21 ` Kai Krakow [this message]
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=khdi5a-sfp.ln1@hurikhan.ath.cx \
--to=hurikhan77+btrfs@gmail.com \
--cc=linux-btrfs@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