Hide Forgot
Additional information: Alok requested via email that we need to include KB article [https://access.redhat.com/solutions/2610101] under erasure coding section in the admin guide and publish the guide async.
As discussed earlier today, most of the information in the bug is already in the document as part of normal performance tuning. performance.client-io-threads is being added to the document as part of the RHGS 3.2 release, as it was unsupported for a time client.event-threads is documented in the tuning section of the Administration Guide, although it recommends 3 threads rather than 4 - is this change significant enough to add specifically to the dispersed, distributed-dispersed sections? Should we update to recommend 4 threads generally? Likewise, cluster.lookup-optimize is mentioned as a general recommendation for small file workloads, so nothing to change here. Alok, Anjana, what are your thoughts here?
Hi Laura/Anjana, I don't see any changes or mention of the KS article under Erasure coding section. Point me the link if I missed out
looks good to me. However the default of client.event-threads remains to be 2 but we are recommending user to set to 4 for better perf
And as discussed on mail, there is no KS link being provided in the doc, but we are making sure all the options mentioned in the KS doc is available in the admin doc