From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Calvin Walton <calvin.walton@kepstin.ca>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: shall I use BTRFS sub-volumes for top-level directories ?
Date: Tue, 19 May 2015 15:16:28 +0200 [thread overview]
Message-ID: <555B37AC.6090307@gmx.de> (raw)
In-Reply-To: <1431539167.9076.9.camel@kepstin.ca>
On 05/13/2015 07:46 PM, Calvin Walton wrote:
> As with all things, it's probably best if you just try it and see!
After the a week both the iowait spikes and the mean value of iowait cycles are decreased - so it was worth here to switch to btrfs subvolumes.
--
Toralf
pgp key: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 0076 E94E
--
"; the past is all dirty and cruel in the modern popular imagination, with the exception of the Romans, who are just cruel"
Ian Mortimer, 2008, "The Time Traveller's Guide to Medieval England"
next prev parent reply other threads:[~2015-05-19 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 14:13 shall I use BTRFS sub-volumes for top-level directories ? Toralf Förster
2015-05-13 17:46 ` Calvin Walton
2015-05-19 13:16 ` Toralf Förster [this message]
2015-05-21 14:39 ` Toralf Förster
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=555B37AC.6090307@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=calvin.walton@kepstin.ca \
--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;
as well as URLs for NNTP newsgroup(s).