All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Cc: Chris Samuel <chris@csamuel.org>
Subject: Re: speeding up slow btrfs filesystem
Date: Sat, 17 Dec 2011 13:00:29 +0100	[thread overview]
Message-ID: <201112171300.29833.Martin@lichtvoll.de> (raw)
In-Reply-To: <201112172211.25456.chris@csamuel.org>

Am Samstag, 17. Dezember 2011 schrieb Chris Samuel:
> On Sat, 17 Dec 2011 04:51:51 AM Martin Steigerwald wrote:
> > Currently I have:
> > 
> > deepdance:~> cat /proc/version
> > Linux version 3.0.0-2-686-pae (Debian 3.0.0-6)
> 
> You are using a fairly old kernel btrfs-wise, I believe there's been
> work done in the 3.2 rc's to improve performance so I'd suggest it's
> well worth testing with 3.2-rc6 to see whether that helps.

I am now using 3.2-rc4 from Debian package already. Currently I do not 
build own kernels.

I have the subjective impression that after the initial rebuild of the 
inode cache it became faster.

I have the following mount options:

deepdance:~> grep btrfs /proc/mounts
/dev/mapper/deepdance-debian / btrfs rw,relatime,space_cache,inode_cache 0 
0
/dev/mapper/deepdance-home /home btrfs rw,relatime,space_cache,inode_cache 
0 0

Might be good to use noatime for harddisks as well.

BTW on my ThinkPad T520 I do not perceive performance issues for BTRFS as 
/. But then thats located on an Intel SSD 320 where seeks should not 
matter much.

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

  reply	other threads:[~2011-12-17 12:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16 17:51 speeding up slow btrfs filesystem Martin Steigerwald
2011-12-16 17:54 ` Martin Steigerwald
2011-12-16 18:38   ` Goffredo Baroncelli
2011-12-16 19:53     ` Martin Steigerwald
2011-12-16 20:58       ` Martin Steigerwald
2011-12-17  7:03         ` Sergei Trofimovich
2011-12-17 11:09           ` Martin Steigerwald
2011-12-17 11:26             ` Hugo Mills
2011-12-17 11:38               ` Martin Steigerwald
2011-12-17 11:45                 ` Hugo Mills
2011-12-17 11:57                   ` Martin Steigerwald
2011-12-17 16:35                   ` Martin Steigerwald
2011-12-17 17:27                     ` Hugo Mills
2011-12-17 11:39       ` Goffredo Baroncelli
2011-12-18 18:41     ` Andrea Gelmini
2011-12-20 19:46       ` Goffredo Baroncelli
2011-12-17 11:11 ` Chris Samuel
2011-12-17 12:00   ` Martin Steigerwald [this message]
2011-12-17 12:42     ` David McBride
2011-12-17 16:14       ` Martin Steigerwald
2011-12-17 11:54 Martin Steigerwald
2011-12-17 12:02 ` Martin Steigerwald
2011-12-17 12:50 ` Goffredo Baroncelli
2011-12-17 16:10   ` Martin Steigerwald

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=201112171300.29833.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=chris@csamuel.org \
    --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 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.