From: Roman Mamedov <rm@romanrm.net>
To: Juan Alberto Cirez <jacirez@rdcsafety.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS on production: NVR 16+ IP Cameras
Date: Fri, 16 Nov 2018 01:18:54 +0500 [thread overview]
Message-ID: <20181116011854.0f1d1c9a@natsu> (raw)
In-Reply-To: <bf338fb1-11fe-baea-4099-af9dc267e597@rdcsafety.com>
On Thu, 15 Nov 2018 11:39:58 -0700
Juan Alberto Cirez <jacirez@rdcsafety.com> wrote:
> Is BTRFS mature enough to be deployed on a production system to underpin
> the storage layer of a 16+ ipcameras-based NVR (or VMS if you prefer)?
What are you looking to gain from using Btrfs on an NVR system? It doesn't
sound like any of its prime-time features -- such as snapshots, checksumming,
compression or reflink copying -- are a must for a bulk video recording
scenario.
And even if you don't need or use those features, you still pay the price for
having them, Btrfs can be 2x to 10x slower than its simpler competitors:
https://www.phoronix.com/scan.php?page=article&item=linux418-nvme-raid&num=2
If you just meant to use its multi-device support instead of a separate RAID
layer, IMO that can't be considered prime-time or depended upon in production
(yes, not even RAID 1 or 10).
--
With respect,
Roman
next prev parent reply other threads:[~2018-11-15 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 18:39 BTRFS on production: NVR 16+ IP Cameras Juan Alberto Cirez
2018-11-15 19:51 ` Nikolay Borisov
2018-11-16 13:39 ` Anand Jain
2018-11-15 20:18 ` Roman Mamedov [this message]
2018-11-16 12:26 ` Austin S. Hemmelgarn
2018-11-17 0:18 ` Chris Murphy
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=20181116011854.0f1d1c9a@natsu \
--to=rm@romanrm.net \
--cc=jacirez@rdcsafety.com \
--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).