Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Kai Krakow <hurikhan77+btrfs@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: exploit preload daemon to defragment most needed files
Date: Sun, 05 May 2013 11:42:24 +0200	[thread overview]
Message-ID: <05mh5a-iqe.ln1@hurikhan.ath.cx> (raw)

[-- Attachment #1: Type: text/plain, Size: 899 bytes --]

Hey list,

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.

While I'd like to read some feedback from the community, maybe collect some 
more ideas, I already discovered one drawback which is a show-stopper: btrfs 
won't defragment files currently in use (probably memory-mapped files only 
but these are a lot while a desktop env is running). I didn't look into it 
any closer yet. And I didn't run benchmarks. But my first impressions are 
that preloading is a bit faster and less io-intensive.

Regards,
Kai

[1]: https://gist.github.com/kakra/5520200

[-- Attachment #2: defrag-preloaded.rb --]
[-- Type: application/x-ruby, Size: 600 bytes --]

             reply	other threads:[~2013-05-05  9:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-05  9:42 Kai Krakow [this message]
2013-05-05 13:57 ` exploit preload daemon to defragment most needed files Tomasz Torcz
2013-05-05 16:21   ` Kai Krakow

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=05mh5a-iqe.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