[Gluster-users] Improving afr performance
raghavendra.hg at gmail.com
Fri Nov 20 20:50:43 UTC 2009
On Fri, Nov 20, 2009 at 10:35 AM, Paras Fadte <plfgoa at gmail.com> wrote:
> Hi Vikas,
> Thanks for the response.
> I am having performance issues upon migration to gluster. Follwoing
> should explain the issue.
> There are scripts running which access data from the gluster mount
> point . Earlier NFS was used . With NFS the scripts seem to have no
> problem getting completed faster but when same scripts run accessing
> same data from gluster it runs about 3-4 times slower . Mostly the
> scripts do stat/unlinking/renaming operations on files. Number of
> files would be roughly 25k withe average file size 40KB . What can be
> done to increase the speed/performance ?
If you are doing only operations like stat which modify metadata, without
reading or writing, stat-prefetch should be enough. If you are reading
files, you can try quick-read, since your file sizes happen to be smaller.
And if you are re-reading you can try io-cache. If you are writing to files,
write-behind should help.
> Regarding stat-prefetch is the following usage correct ?
> volume afr
> type cluster/replicate
> subvolumes A B
> volume stat-prefetch
> type performance/stat-prefetch
> subvolumes afr
> Thank you.
> On Fri, Nov 20, 2009 at 1:42 AM, Vikas Gorur <vikas at gluster.com> wrote:
> > Paras Fadte wrote:
> >> Hi,
> >> Which settings in AFR in gluster directly affects performance when
> >> there are lots of "ls" and "stat" calls made on files mounted using
> >> gluster?
> > There isn't any setting in afr that can affect ls or stat performance.
> > can load
> > the stat-prefetch translator above afr to increase ls/stat performance.
> > Vikas
> Gluster-users mailing list
> Gluster-users at gluster.org
More information about the Gluster-users