Re: What application workloads are too slow for you on gluster?

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

 



No problems with web hosting here, including loads of busy Wordpress sites & the like. However you need to tune your filesystems correctly.
In our case, we've got webserver VMs running on top of a Gluster layer with the following configurations...

Joe's even written a page about optimisations.

In all, the filesystem is only touched when a user uploads a file. Everything else pretty much runs in memory.

This problem isn't so much Gluster's fault, as people trying to use a distributed filesystem/volume like a local disk.


On 24 September 2016 at 20:36, Pranith Kumar Karampuri <pkarampu@xxxxxxxxxx> wrote:


On Sat, Sep 24, 2016 at 8:59 PM, Kevin Lemonnier <lemonnierk@xxxxxxxxx> wrote:
On Sat, Sep 24, 2016 at 07:48:53PM +0530, Pranith Kumar Karampuri wrote:
>    hi,
>    A A A A A  I want to get a sense of the kinds of applications you tried
>    out on gluster but you had to find other alternatives because gluster
>    didn't perform well enough or the soultion would become too expensive if
>    you move to all SSD kind of setup.

Hi,

Web Hosting is what comes to mind for me. Applications like prestashop, wordpress,
some custom apps ... I know that I try to use DRBD as much as I can for that since
GlusterFS makes the sites just way too slow to use, I tried both fuse and NFS (not
ganesha since I'm on debian everytime though, don't know if that matters).
Using things like OPCache and moving the application's cache outside of the volume
are helping a lot but that brings a whole loads of other problems you can't always
deal with, so most of the time I just don't use gluster for that.

Last time I really had to use gluster to host a web app I ended up installing a VM
with a disk stored on glusterfs and configuring a simple NFS server, that was way
faster than mounting a gluster volume directly on the web servers. At least that
proves VM hosting works pretty well now though !

Now I can't try tiering, unfortunatly I don't have the option of having hardware for
that, but maybe that would indeed solve it if it makes looking up lots of tiny files
quicker.

I guess website hosting could be small-file workload related? Tiering may not help here until we reduce network round trips. I was wondering if anyone has any write intensive workload that gluster couldn't keep up with and they had to move to SSDs to make sure gluster works fine with it.
 

--
Kevin Lemonnier
PGP Fingerprint : 89A5 2283 04A0 E6E9 0111

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users



--
Pranith

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.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