Gluster users - Feb 2015 - how to shrink client translator

>> Hi,
>>
>> With glusterfs version 3.6.1,there are so many translator in  my client
>> *.vol ,how to shrink some ,such as "debug/io-stats" and
>> "performance/open-behind".
>>
>>
>gluster volume set <volname> open-behind off turns off this xlator in 
>the client stack. There is no way to turn off debug/io-stats. Any reason 
>why you would like to turn off io-stats translator?
>Regards,
>Vijay
For improving efficiency.

Is there any command to show the current translator tree after dynamic 
adding or deletting any xlator?

Regards
Bin.Yang
--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail (and any
attachment transmitted herewith) is privileged and confidential and is intended
for the exclusive use of the addressee(s).  If you are not an intended
recipient, any disclosure, reproduction, distribution or other dissemination or
use of the information contained is strictly prohibited.  If you have received
this mail in error, please delete it and notify us immediately.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20150202/1c8779c8/attachment.html>

> >gluster volume set <volname> open-behind off turns off this
xlator in
> >the client stack. There is no way to turn off debug/io-stats. Any
reason
> >why you would like to turn off io-stats translator?
>
> For improving efficiency.
It might not be a very fruitful kind of optimization.  Repeating an
experiment someone else had done a while ago, I just ran an experiment to
compare a normal client volfile vs. one with a *hundred* extra do-nothing
translators added.  There was no statistically significant difference,
even on a fairly capable SSD-equipped system.  I/O latency variation and
other general measurement noise still far outweigh the cost of a few extra
function calls to invoke translators that aren't doing any I/O themselves.
> Is there any command to show the current translator tree after dynamic
adding
> or deletting any xlator?
The new graph should show up in the logs.  Also, you can always use
"gluster
system getspec xxx" to get the current client volfile for any volume xxx.