Bug 1511506 - Doc RFE - Document how to set the readdir-chunk option
Summary: Doc RFE - Document how to set the readdir-chunk option
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: doc-Administration_Guide
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.4.0
Assignee: Chandrakanth Pai
QA Contact: Manisha Saini
URL:
Whiteboard:
: 1518170 (view as bug list)
Depends On:
Blocks: 1503140
TreeView+ depends on / blocked
 
Reported: 2017-11-09 13:30 UTC by Anjana Suparna Sriram
Modified: 2018-09-10 15:27 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-10 15:27:50 UTC


Attachments (Terms of Use)

Description Anjana Suparna Sriram 2017-11-09 13:30:49 UTC
Additional information: 

Use Case Description: 

As an administrator, I want to know how I can set the readdir-chunk option so that I can complete command operations quickly.

This use case includes documenting the following content:

Provide brief overview information about the performance improvements available by setting the readdir-chunk option to provide task information that describes where and how to set the readdir-chunk option to provide a list of options that are required to be enabled/set in order to implement readdir-chunk

PoC: Frank/Kaleb/Soumya

Comment 2 Frank Filz 2017-12-15 17:36:44 UTC
Are you looking for good values to use, or how to configure? On the latter part, dirent chunking becomes the default with it's introduction to the code base. For tuning, I haven't done any work.

Comment 5 Frank Filz 2018-02-07 14:26:54 UTC
So far based on Ambarish's testing, it seems that the default of 128 is the sweet spot (lucky choice on my part I guess). At this point I would not advise tuning this option.

Comment 7 Anjana Suparna Sriram 2018-02-16 07:18:10 UTC
*** Bug 1518170 has been marked as a duplicate of this bug. ***

Comment 12 Daniel Gryniewicz 2018-03-05 15:03:14 UTC
I think at the moment we don't recommend anyone change it.

Comment 13 Kaleb KEITHLEY 2018-03-06 15:47:51 UTC
We seem to be going around in circles on this. I'm not sure why.

It is a setting that _can_ be changed. We strongly suggest (recommend) that it be left at the default setting of 128. We don't have any guidance at this time for the circumstances under which anyone should change it, or what they should change it to.

But if a user wants to experiment, they certainly may.

AFAIK we don't have any "secret" or undocumented settings. And even if we do, people can look at the source to find it. The best we can do is document that it is a setting, and we think it should be left at the default value of 128.

Either that, or don't document it. At all, or ever, or until we have advice for when to set it to something else.

Comment 14 Ambarish 2018-03-06 15:54:55 UTC
(In reply to Kaleb KEITHLEY from comment #13)
> We seem to be going around in circles on this. I'm not sure why.
> 
> It is a setting that _can_ be changed. We strongly suggest (recommend) that
> it be left at the default setting of 128. We don't have any guidance at this
> time for the circumstances under which anyone should change it, or what they
> should change it to.
> 
> But if a user wants to experiment, they certainly may.
> 
> AFAIK we don't have any "secret" or undocumented settings. And even if we
> do, people can look at the source to find it. The best we can do is document
> that it is a setting, and we think it should be left at the default value of
> 128.
> 
> Either that, or don't document it. At all, or ever, or until we have advice
> for when to set it to something else.

+1.

As mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1511506#c6 , I think we can go ahead document how to tweak it , with a very clear recommendation of NOT to tweak it.

Comment 15 Frank Filz 2018-03-06 18:28:11 UTC
(In reply to Ambarish from comment #14)
> (In reply to Kaleb KEITHLEY from comment #13)
> > We seem to be going around in circles on this. I'm not sure why.
> > 
> > It is a setting that _can_ be changed. We strongly suggest (recommend) that
> > it be left at the default setting of 128. We don't have any guidance at this
> > time for the circumstances under which anyone should change it, or what they
> > should change it to.
> > 
> > But if a user wants to experiment, they certainly may.
> > 
> > AFAIK we don't have any "secret" or undocumented settings. And even if we
> > do, people can look at the source to find it. The best we can do is document
> > that it is a setting, and we think it should be left at the default value of
> > 128.
> > 
> > Either that, or don't document it. At all, or ever, or until we have advice
> > for when to set it to something else.
> 
> +1.
> 
> As mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1511506#c6 , I
> think we can go ahead document how to tweak it , with a very clear
> recommendation of NOT to tweak it.

+1

Comment 16 Kaleb KEITHLEY 2018-05-03 11:46:15 UTC
If you must have additional words, then probably something like

"Do not change this setting without doing extensive testing of your work load."

Comment 26 Manisha Saini 2018-08-30 17:04:43 UTC
Verified. The changes has been reverted.
Thanks


Note You need to log in before you can comment on or make changes to this bug.