----- Original Message ----- > From: "Uthra R. Rao (GSFC-672.0)[ADNET SYSTEMS INC]" <uthra.r.rao@xxxxxxxx> > To: "Vijay Bellur" <vbellur@xxxxxxxxxx> > Cc: gluster-users@xxxxxxxxxxx > Sent: Monday, November 30, 2015 11:32:33 AM > Subject: RE: Glusterfs - Translators/Performance > > Thank you Vijay for taking the time to reply. > > What we want is writes to be a bit better than the 10MBps we are seeing but > not as important as read which is good at 400MBps. > > Is it better to store settings in /etc/glusterfs/glusterd.vol (as in the > docs) or with "gluster set" (on command line as most posts seem to use)?se settings in /etc/glusterfs/glusterd.vol are meant for the management daemon i.e. glusterd. All tuning needed for volume services would need to be done through the "gluster volume set" interface. > > Does only one of performance/io-threads, performance/io-cache, > performance/writebehind translators take effect or are they all in effect? > Are they ON by default? > Yes, all these translators are ON by default. > We currently only installed gluster client on our clients, which doesn't have > the gluster command for settings the properties. > Should we install gluster server on our clients also to change gluster client > properties? > gluster client properties cannot be set per client through "volume set" CLI. The properties altered through "volume set" are applicable to all clients by default. Per client behavior can be altered at the time of mounting a gluster volume. Regards, Vijay _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
