From: Martin Steigerwald <Martin@lichtvoll.de>
To: Goffredo Baroncelli <kreijack@inwind.it>, linux-btrfs@vger.kernel.org
Subject: Re: speeding up slow btrfs filesystem
Date: Sat, 17 Dec 2011 17:10:52 +0100 [thread overview]
Message-ID: <201112171710.53140.Martin@lichtvoll.de> (raw)
In-Reply-To: <2297283.SPUU0GRYgu@venice>
Am Samstag, 17. Dezember 2011 schrieb Goffredo Baroncelli:
> > Adding new possibilities is one thing. And supporting snapshots
> > properly would depend on some support side from the applications. I
> > think that using snapshots for upgrades is a good idea.
> >
> >=20
> >
> > But OTOH I think that BTRFS should not break or slow down existing
> > userspace. I think that existing approaches like using fsync() like
> > according to quite some filesystem developers it should be used
> > should continue to work nicely.
>=20
> Nobody wants to slowdown the application. But the life is full of
> compromises. If you want the speed of ext4, you can use ext4. If you
> want the snapshot capability and the COW guarantee you can use BTRFS,
> but you have some slowness.
>=20
> Of course the best would be have the speed of the ext4 with the
> capabilities of btrfs.... :-) Unfortunately today this is not
> available.
Its perfectly acceptable for me that BTRFS does not deliver this yet.
I understood your initial answer that its just that BTRFS is different =
and=20
thus performs poorly in fsync() based workloads and thats about it. Tha=
t=20
its a principal issue. That part I didn=B4t agree too. Heck from the de=
sign=20
differences of COW filesystem it might even be some sort of a principal=
=20
issue. But then I like to see this as a challenge, not as a show stoppe=
r.
Actually for me especially for that Amarok Thinkpad T23 there is no hur=
ry.=20
Its play BTRFS play machine. I just want to see what I can do with=20
filesystem maintenance to bring it up to speed.
Everything else is following development and upgrading kernels ;).
Thanks,
--=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
next prev parent reply other threads:[~2011-12-17 16:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 11:54 speeding up slow btrfs filesystem Martin Steigerwald
2011-12-17 12:02 ` Martin Steigerwald
2011-12-17 12:50 ` Goffredo Baroncelli
2011-12-17 16:10 ` Martin Steigerwald [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-16 17:51 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
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=201112171710.53140.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=kreijack@inwind.it \
--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.