Gluster's read performance

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

 



Hello All,

I am new to gluster and evaluating it for my production environment. After
reading some blogs and googling I learned that NFS mount at clients give
better read performance for small files and the glusterfs/FUSE mount gives
better for large write operations.

Now my questions are

1) What do we mean by small files? 1KB/1MB/1GB?
2) If I am using NFS mount at the client I am most likely loosing the high
availability feature of gluster. unlike fuse mount where if primary goes
down I don't need to worry about availability.

Basically my production environment will mostly have read operations of
files ranging from 400KB to 5MB and they will be concurrently read by
different threads.

Thanks,
Chandan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gluster.org/pipermail/gluster-users/attachments/20120920/40cd5444/attachment.htm>


[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