linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Cc: David McBride <dwm@doc.ic.ac.uk>
Subject: Re: speeding up slow btrfs filesystem
Date: Sat, 17 Dec 2011 17:14:25 +0100	[thread overview]
Message-ID: <201112171714.25563.Martin@lichtvoll.de> (raw)
In-Reply-To: <1324125748.22624.14.camel@squire.doc.ic.ac.uk>

Am Samstag, 17. Dezember 2011 schrieb David McBride:
> On Sat, 2011-12-17 at 13:00 +0100, Martin Steigerwald wrote:
> > 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.
>=20
> Okay, that would be consistent with the slow behaviour observed by
> others on fsync()-heavy workloads.  Presumably this produces much mor=
e
> seeky IO patterns than current common filesystems; I wonder if this i=
s
> a limitation of the current implementation or something that is an
> inherent properties of the data-structures being used?

All I can say is that the ThinkPad T520 doesn=C2=B4t seem the best mach=
ine for=20
testing the performance of software. I have seen nothing thats actually=
=20
been slow on that machine yet. Its not a machine for triggering=20
bottlenecks easily it seems to me.

--=20
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-12-17 16:14 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
2011-12-17 12:42     ` David McBride
2011-12-17 16:14       ` Martin Steigerwald [this message]
  -- strict thread matches above, loose matches on Subject: below --
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=201112171714.25563.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=dwm@doc.ic.ac.uk \
    --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).