From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Hugo Mills <hugo@carfax.org.uk>,
Martin Tippmann <martin.tippmann@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: FYIO: A rant about btrfs
Date: Thu, 17 Sep 2015 07:31:59 -0400 [thread overview]
Message-ID: <55FAA4AF.6040909@gmail.com> (raw)
In-Reply-To: <20150916233114.GE28645@carfax.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
On 2015-09-16 19:31, Hugo Mills wrote:
> On Wed, Sep 16, 2015 at 03:21:26PM -0400, Austin S Hemmelgarn wrote:
>> On 2015-09-16 12:45, Martin Tippmann wrote:
>>> 2015-09-16 17:20 GMT+02:00 Austin S Hemmelgarn <ahferroin7@gmail.com>:
>>> [...]
> [...]
>>> From reading the list I understand that btrfs is still very much work
>>> in progress and performance is not a top priority at this stage but I
>>> don't see why it shouldn't perform at least equally good as ZFS/F2FS
>>> on the same workloads. Is looking at performance problems on the
>>> development roadmap?
>> Performance is on the roadmap, but the roadmap is notoriously
>> short-sighted when it comes to time-frame for completion of
>> something. You have to understand also that the focus in BTRFS has
>> also been more on data safety than performance, because that's the
>> intended niche, and the area most people look to ZFS for.
>
> Wait... there's a roadmap? ;)
>
Yeah, maybe it's better to say that there's a directed graph of feature
interdependence. I was just basing my statement on the presence of a
list of project ideas on the wiki. :)
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
next prev parent reply other threads:[~2015-09-17 11:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 14:43 FYIO: A rant about btrfs M G Berberich
2015-09-16 15:20 ` Austin S Hemmelgarn
2015-09-16 16:25 ` Zia Nayamuth
2015-09-16 19:08 ` Austin S Hemmelgarn
2015-09-16 23:29 ` Hugo Mills
2015-09-17 15:57 ` Martin Steigerwald
2015-09-18 13:06 ` Austin S Hemmelgarn
2015-09-16 16:45 ` Martin Tippmann
2015-09-16 19:21 ` Austin S Hemmelgarn
2015-09-16 23:31 ` Hugo Mills
2015-09-17 11:31 ` Austin S Hemmelgarn [this message]
2015-09-17 14:52 ` Aneurin Price
2015-09-18 13:10 ` Austin S Hemmelgarn
2015-09-24 16:38 ` Aneurin Price
2015-09-17 2:07 ` Rich Freeman
2015-09-16 16:53 ` Vincent Olivier
[not found] ` <A4269DC6-6CD6-4E8C-B3C9-5F5DDBE86911@up4.com>
2015-09-16 18:22 ` Austin S Hemmelgarn
2015-09-16 19:04 ` Vincent Olivier
2015-09-16 19:36 ` Austin S Hemmelgarn
2015-09-16 22:08 ` Zygo Blaxell
2015-09-18 0:34 ` Duncan
2015-09-18 13:12 ` Austin S Hemmelgarn
2015-09-16 22:25 ` Duncan
2015-09-23 20:39 ` Josef Bacik
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=55FAA4AF.6040909@gmail.com \
--to=ahferroin7@gmail.com \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=martin.tippmann@gmail.com \
/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).