<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:11:59 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-7795] least_qunit should be tunnable</title>
                <link>https://jira.whamcloud.com/browse/LU-7795</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;In order to better adjust filesystem performance when using quotas we would like to have a tunable least_qunit option.  &lt;/p&gt;</description>
                <environment></environment>
        <key id="34784">LU-7795</key>
            <summary>least_qunit should be tunnable</summary>
                <type id="4" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11310&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</priority>
                        <status id="5" iconUrl="https://jira.whamcloud.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="niu">Niu Yawei</assignee>
                                    <reporter username="mhanafi">Mahmoud Hanafi</reporter>
                        <labels>
                    </labels>
                <created>Thu, 18 Feb 2016 20:25:33 +0000</created>
                <updated>Wed, 4 Dec 2019 09:07:29 +0000</updated>
                            <resolved>Fri, 27 May 2016 12:47:00 +0000</resolved>
                                    <version>Lustre 2.5.3</version>
                                    <fixVersion>Lustre 2.9.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                            <comments>
                            <comment id="143003" author="pjones" created="Fri, 19 Feb 2016 18:17:30 +0000"  >&lt;p&gt;Niu&lt;/p&gt;

&lt;p&gt;Could you please comment on this suggestion?&lt;/p&gt;

&lt;p&gt;Thanks&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="143011" author="adilger" created="Fri, 19 Feb 2016 18:51:38 +0000"  >&lt;p&gt;Mahmoud, could you please explain a bit on how you want to tune the least_qunit?  Do you want to increase it or decrease it, what performance impact do you see today, and how do you expect the tuning of least_qunit to change the performance?&lt;/p&gt;</comment>
                            <comment id="143265" author="mhanafi" created="Mon, 22 Feb 2016 21:19:37 +0000"  >&lt;p&gt;We have reports from users that when they exceed their soft quota there is significant performance impact. We had reported this in &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-4139&quot; title=&quot;Significant perforamce issue when user over soft quota limit&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-4139&quot;&gt;&lt;del&gt;LU-4139&lt;/del&gt;&lt;/a&gt; and was address to some extent, but we would want more controller over qunit allocation in such situations.  &lt;/p&gt;
</comment>
                            <comment id="143295" author="niu" created="Tue, 23 Feb 2016 03:13:02 +0000"  >&lt;p&gt;Hi, Mahmoud , according to the numbers in &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-4139&quot; title=&quot;Significant perforamce issue when user over soft quota limit&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-4139&quot;&gt;&lt;del&gt;LU-4139&lt;/del&gt;&lt;/a&gt;, looks the performance is reasonable after the fixing:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Direct I/O&lt;br/&gt;
UnderSoftlimit: 383MB/sec&lt;br/&gt;
OverSoftlimit: 359MB/sec&lt;br/&gt;
Buffered I/O&lt;br/&gt;
UnderSoftlimit:316MB.sec&lt;br/&gt;
OverSoftlimit: 304MB/sec&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Is your proposal to let user set a larger least_qunit so that the performance won&apos;t drop even after over soft limit? One thing worth noting is that larger least_qunit means worse limit/grace time accuracy, so we have to do some sort of compromise here. What do you think about?&lt;/p&gt;</comment>
                            <comment id="143625" author="mhanafi" created="Wed, 24 Feb 2016 18:16:56 +0000"  >&lt;p&gt;I think there are some IO patterns that are effected by the softquota limit then others. At least that is what our users are reporting. Since most of our quota are 100&apos;sTB and we have large gap between soft and hard quota we are willing to give up limit/grace time accuracy for no lost of performance. &lt;/p&gt;</comment>
                            <comment id="145215" author="niu" created="Fri, 11 Mar 2016 04:06:27 +0000"  >&lt;p&gt;I see, the requirement makes sense to me, but I don&apos;t think tuning the least_qunit is a proper way, because it affects the hard limit as well.&lt;/p&gt;

&lt;p&gt;A better way is to add a proc interface to quota master (qmt), and user may turn off the qunit adjustment for soft limit (no qunit adjustment even if soft limit is exceeded) via this interface. Of course, people should be warned that grace time accuracy will be lost when he turns it off.&lt;/p&gt;

&lt;p&gt;I can compose a patch if you don&apos;t against. Thanks.&lt;/p&gt;</comment>
                            <comment id="145218" author="mhanafi" created="Fri, 11 Mar 2016 07:22:04 +0000"  >&lt;p&gt;Are you purposing a per-user setting or global for a filesystem? Turn off qunit adjustment must a admin only function.&lt;/p&gt;</comment>
                            <comment id="145219" author="niu" created="Fri, 11 Mar 2016 08:32:01 +0000"  >&lt;p&gt;It&apos;s global setting, and least qunit is also a global parameter.&lt;/p&gt;</comment>
                            <comment id="145240" author="mhanafi" created="Fri, 11 Mar 2016 16:09:58 +0000"  >&lt;p&gt;That sounds like what we would need.&lt;/p&gt;</comment>
                            <comment id="145388" author="gerrit" created="Mon, 14 Mar 2016 07:06:32 +0000"  >&lt;p&gt;Niu Yawei (yawei.niu@intel.com) uploaded a new patch: &lt;a href=&quot;http://review.whamcloud.com/18896&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/18896&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7795&quot; title=&quot;least_qunit should be tunnable&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7795&quot;&gt;&lt;del&gt;LU-7795&lt;/del&gt;&lt;/a&gt; quota: tuneable soft least qunit&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: 601fa84017a98450432d5cb3dbdea0cd8b82e056&lt;/p&gt;</comment>
                            <comment id="145887" author="jaylan" created="Thu, 17 Mar 2016 00:20:16 +0000"  >&lt;p&gt;Can you provide a back port to 2.5.3-fe?&lt;br/&gt;
It is not obvious to me how to resolve the conflicts on lprocfs_quota_qpi_vars declaration.&lt;/p&gt;

&lt;p&gt;Thanks!&lt;/p&gt;</comment>
                            <comment id="145905" author="niu" created="Thu, 17 Mar 2016 07:56:35 +0000"  >&lt;p&gt;Here is the port to b2_5_fe: &lt;a href=&quot;http://review.whamcloud.com/#/c/18976/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#/c/18976/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="146010" author="mhanafi" created="Thu, 17 Mar 2016 19:40:15 +0000"  >&lt;p&gt;With this patch when is client sync writes triggered?&lt;/p&gt;</comment>
                            <comment id="146055" author="niu" created="Fri, 18 Mar 2016 02:25:06 +0000"  >&lt;p&gt;The client sync write will be triggered when approaching/exceeding hard limit, if there is no hard limit, sync write won&apos;t be triggered. &lt;/p&gt;</comment>
                            <comment id="153771" author="gerrit" created="Fri, 27 May 2016 00:57:42 +0000"  >&lt;p&gt;Oleg Drokin (oleg.drokin@intel.com) merged in patch &lt;a href=&quot;http://review.whamcloud.com/18896/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/18896/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7795&quot; title=&quot;least_qunit should be tunnable&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7795&quot;&gt;&lt;del&gt;LU-7795&lt;/del&gt;&lt;/a&gt; quota: tuneable soft least qunit&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: 0cadce268a09a94824b82bc1a61e98963582c423&lt;/p&gt;</comment>
                            <comment id="153804" author="pjones" created="Fri, 27 May 2016 12:47:00 +0000"  >&lt;p&gt;Landed for 2.9&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                                        </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="21613">LU-4139</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                            <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzy1sn:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>