linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: "Swâmi Petaramesh" <swami@petaramesh.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Rebalance makes BTRFS 10x slower
Date: Sun, 23 Mar 2014 16:12:07 +0100	[thread overview]
Message-ID: <7616233.4PhybLsPIr@merkaba> (raw)
In-Reply-To: <4392627.HWimVooIO4@tethys>

Am Sonntag, 23. März 2014, 15:51:34 schrieben Sie:
> I was expecting either a speed improvement after rebalance, or no
> noticeable  effect, but I am extremely disappointed to see that now (and
> after having rebooted), my system has become slow like hell, takes at least
> 10x longer to boot and operate, to the point it has become hardly usable
> 
> I would have thought a rebalance would have improved the filesystem 
> organization, looks like it's the absolute contrary

I also found this to be the case as I rebalanced the root filesystem of my 
Debian installation on this ThinkPad T520 on an Intel SSD 320.

It doubled the boot time that systemd-analayze rebootet back then.

apt-get dist-upgrade was noticably slower to.

Thus I avoid balance unless I really need it.

For migrating of /home to BTRFS RAID 1 on Intel SSD 320 + Crucial mSATA M500 
SSD I did a balance to switch to RAID 1. Probably /home would be faster 
recreating it from scratch and restoring from backup tough.

Especially MySQL based Akonadi seems to be slower than with /home on a single 
SSD, but that might also be due to that amount of mails in Linux kernel-ml 
folder raising to a high amount (and inefficiencies in Akonadi).

-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

  reply	other threads:[~2014-03-23 15:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-23 14:51 Rebalance makes BTRFS 10x slower Swâmi Petaramesh
2014-03-23 15:12 ` Martin Steigerwald [this message]
2014-04-13 14:16   ` Clemens Eisserer
2014-04-13 20:46     ` Duncan
2014-04-16 15:00       ` Clemens Eisserer

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=7616233.4PhybLsPIr@merkaba \
    --to=martin@lichtvoll.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=swami@petaramesh.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).