linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjammin2068 <benjammin2068@gmail.com>
To: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Recommendation on new system Arrays
Date: Tue, 10 Jan 2017 02:48:22 -0600	[thread overview]
Message-ID: <bfb6ebec-defe-186d-76c8-f7fbbaf65a70@gmail.com> (raw)
In-Reply-To: <d1f5b65b-5a0b-92e1-7fe7-d2a0c45c8998@fnarfbargle.com>

On 01/08/2017 10:34 PM, Brad Campbell wrote:
>
> This can be a real trap.
>
> In general CCTV software works great for about the first 2 complete database writes. As the database ages you will find increasing levels of write fragmentation that kill your write latency. It also makes each write smaller as you are no longer streaming bulk data to disk but filling the holes left by expired footage. This destroys your array write latency and makes replay and searching for footage frustratingly slow.
>
> Make sure your CCTV storage RAID is not used for anything else, select a small chunk size to minimise stripe size and be prepared for fairly high search and playback latency.
>
> Most of the major CCTV systems suffer in the same way, and they generally get around it by using "hardware" RAID cards with large RAM buffers (until the BBU wears out and you start getting massive footage loss because they can't get the streams to disk fast enough).
>
> If performance is not an issue then a RAID6 being written from a Windows VM on a Linux host works just fine. Pass the md straight through to the Windows VM and let it manage the raw block device.
>
> It has bee a couple of years since I tested Milestone, but I've just finished a test with Indigo Vision, Aimetis, Genetec, Geutebruck, Bosch, Avigilon & March Networks. They all suffer to a certain degree and all use different storage architectures depending on their legacy. March works really well over SMB shares though. I'm just not fond of the product.
>
> Milestone sent me a new test license before Christmas but I've not got around to spooling it up yet.
>
> All of this stuff gets tested on KVM VM's writing to a couple of small RAID-6 arrays (10-14 drives).

Excellent -- the kind of info I was looking for (and wondering about.)

Thanks for the tip!

 -Ben



  parent reply	other threads:[~2017-01-10  8:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06 16:14 Recommendation on new system Arrays Benjammin2068
2017-01-07 10:04 ` Wols Lists
2017-01-08  4:04   ` Benjammin2068
2017-01-08  4:13     ` Stan Hoeppner
2017-01-08  9:07       ` Wols Lists
2017-01-12 15:39     ` Phil Turmel
2017-01-17 18:57       ` Benjammin2068
     [not found] ` <d1f5b65b-5a0b-92e1-7fe7-d2a0c45c8998@fnarfbargle.com>
2017-01-10  8:48   ` Benjammin2068 [this message]
2017-01-10 15:55     ` Wols Lists

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=bfb6ebec-defe-186d-76c8-f7fbbaf65a70@gmail.com \
    --to=benjammin2068@gmail.com \
    --cc=linux-raid@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).