<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Sorry, I should have noted that. 380MB is both read and write (I
confirmed this with a developer).<br>
<br>
We do need the NFS stack, as that's how all the code and various
many Instances work -- we have several "workers" that chop up video
on the same namespace. It's not efficient, but that's how it has to
be for now.<br>
<br>
Redundancy, in terms of the server? We have RAIDED volumes if
that's what you're referring to.<br>
<br>
Here's a basic outline of the flow (as I understand it):<br>
<br>
<br>
Video Capture Agent sends in large file of video (30gb +/-) <br>
<br>
Administrative host receives and writes to NFS<br>
<br>
A process copies this over to another point in the namespace<br>
<br>
Another Instance picks up the file, reads and starts processing and
writes (FFMPEG is involved)<br>
<br>
<br>
Something like that -- I may not have all the steps, but essentially
there's a ton of I/O going on. I know our code model is not
efficient, but it's complicated and can't just be changed (it's
based on an open source product and there's some code baggage).<br>
<br>
We looked into another product that allegedly scaled out using
multiple NFS heads with massive local cache (AWS instances) and
sharing the same space, but it was horrible and just didn't work for
us.<br>
<br>
<br>
<br>
Thank you.<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 7/14/15 3:06 PM, Mathieu Chateau
wrote:<br>
</div>
<blockquote
cite="mid:CACpSnaJX7YaNbFX7O=TOiOC8t+0sa7EfEXZQ8=9J9x=eJ-sjkg@mail.gmail.com"
type="cite">
<div dir="ltr">Hello,
<div><br>
</div>
<div>is it 380MB in read or write ? What level of redundancy do
you need?</div>
<div>do you really need nfs stack or just a mount point (and so
be able to use native gluster protocol) ?</div>
<div><br>
</div>
<div>Gluster load is mostly put on clients, not server (clients
do the sync writes to all replica, and do the memory cache)</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div class="gmail_signature">Cordialement,<br>
Mathieu CHATEAU<br>
<a moz-do-not-send="true" href="http://www.lotp.fr"
target="_blank">http://www.lotp.fr</a></div>
</div>
<br>
<div class="gmail_quote">2015-07-14 20:49 GMT+02:00 Forrest
Aldrich <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:forrie@gmail.com" target="_blank">forrie@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">I'm
exploring solutions to help us achieve high throughput and
scalability within the AWS environment. Specifically, I
work in a department where we handle and produce video
content that results in very large files (30GB etc) that
must be written to NFS, chopped up and copied over on the
same mount (there are some odd limits to the code we use,
but that's outside the scope of this question).<br>
<br>
Currently, we're using a commercial vendor with AWS, with
dedicated Direct Connect instances as the back end to our
production. We're maxing out at 350 to 380 MB/s which is
not enough. We expect our capacity will double or even
triple when we bring on more classes or even other entities
and we need to find a way to squeeze out as much I/O as we
can.<br>
<br>
Our software model depends on NFS, there's no way around
that presently.<br>
<br>
Since GlusterFS uses FUSE, I'm concerned about performance,
which is a key issue. Sounds like a STRIPE would be
appropriate.<br>
<br>
My basic understanding of Gluster is the ability to include
several "bricks" which could be multiples of either
dedicated EBS volumes or even multiple instances of the
above commercial vendor, served up via NFS namespace, which
would be transparently a single namespace to client
connections. The I/O could be distributed in this manner.<br>
<br>
I wonder if someone here with more experience with the above
might elaborate on whether GlusterFS could be used in the
above scenario. Specifically, performance I/O. We'd really
like to gain upwards as much as possible, like 700 Mb/s and
1 GB/s and up if possible.<br>
<br>
<br>
<br>
Thanks in advance.<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a moz-do-not-send="true"
href="http://www.gluster.org/mailman/listinfo/gluster-users"
rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>