Re: Gluster Best Practices

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The proper way to engineer your system would be to identify the performance of your most expensive processes and design a system to allow those to perform in a way that is in line with your expectations.

If you're properly engineering a system, you should know what your performance expectations are before you begin testing to see if you met them.

Also be wary of comparing apples to orchards. Picking a basket of apples to feed 20 people may be the fastest and most efficient way to feed them, but when you have 2000, it's better to just send them in to the orchard to pick their own. Sure, each individuals performance will be degraded, but the overall task is vastly more performant.

On August 11, 2014 1:59:24 AM PDT, Alan Orth <alan.orth@xxxxxxxxx> wrote:
Hi,

I guess some good advice is "pre-mature optimization is the root of all
evil". Use the Gluster defaults for your replica volumes, then, when
you inevitably have performance issues, identify bottlenecks logically
and iteratively:
- Raw RAID read/write speeds
- Raw network read/write speeds

ie, make sure your hardware/network can keep up before trying to "fix"
GlusterFS. We use GlusterFS for home directories on a compute cluster
with 10-20 concurrent users (~100 total users), and I mandate that users
do write-heavy jobs to compute-node local storage. It's a bit different
use case than yours, but hopefully useful insight. For the record,
we're using 10Gbe over copper.

Other than that, the Red Hat storage guide recommends hardware RAID6 and
XFS (rather than ext4).

Cheers,

Alan

On 08/01/2014 10:02 AM, Bruno MACADRÉ wrote:
Hi all,

I'm currently doing a Fileserver between 2 nodes, I use GlusterFS in
replicate mode between them to keep data in sync.

This fileserver is planned to be used by about 200
users/workstations simultaneously for homes and other shares so my
questions are :

* What's the best mount type (GlusterFS or NFS) for performances
and/or stability ?
* I see around the Web a lot of tuning (all and nothing), is
there a tuning concept according to the final use and the hardware of
the servers ?
* Is there some caveat to avoid ?

Thanks by advance for any answers
Regards,
Bruno.



--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux