<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:39:47 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-10967] MDT page cache management improvements</title>
                <link>https://jira.whamcloud.com/browse/LU-10967</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Opening this as somewhat of a catch all for improvements to MDT memory management, either through pinning or making more selective use of the page cache.&#160; This will be important for at least two cases...&lt;br/&gt;
 A) Data On MDT&lt;br/&gt;
 B) Combining OST and MDT on a single server&lt;br/&gt;
 MDT performance historically relied on &quot;read mostly&quot; workload to backing storage, with much of the important and frequently used metatdata in DRAM cache.&#160; With increase in data blocks from either case above, that could quickly get pushed out of cache and thereby slow down metadata ops.&lt;/p&gt;

&lt;p&gt;It may not be practical to try to pin all MDT &quot;real metadata&quot; info in memory, but some features to perhaps release DoM from the page cache faster, or refresh the MDT (and OST) bitmaps and inode tables, would be helpful.&lt;/p&gt;</description>
                <environment>Relevant to any configuration where critical MDT metadata may not fit in memory or may get pushed out of DRAM cache due to other IO.</environment>
        <key id="52042">LU-10967</key>
            <summary>MDT page cache management improvements</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="1" iconUrl="https://jira.whamcloud.com/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="pjones">Peter Jones</assignee>
                                    <reporter username="ndauchy">Nathan Dauchy</reporter>
                        <labels>
                    </labels>
                <created>Mon, 30 Apr 2018 13:28:48 +0000</created>
                <updated>Mon, 30 Apr 2018 21:20:14 +0000</updated>
                                            <version>Lustre 2.10.3</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>8</watches>
                                                                            <comments>
                            <comment id="226941" author="ndauchy" created="Mon, 30 Apr 2018 13:46:00 +0000"  >&lt;p&gt;The other tickets I could find that are even marginally related to this issue...&lt;br/&gt;
    &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-1885&quot; title=&quot;Lustre should be able to limit amount of memory used for read and write caches&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-1885&quot;&gt;&lt;del&gt;LU-1885&lt;/del&gt;&lt;/a&gt; : Lustre should be able to limit amount of memory used for read and write caches&lt;br/&gt;
    &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-2477&quot; title=&quot;Poor MDS create performance due to ARC cache growth&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-2477&quot;&gt;&lt;del&gt;LU-2477&lt;/del&gt;&lt;/a&gt; : Poor MDS create performance due to ARC cache growth&lt;br/&gt;
    &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-10946&quot; title=&quot;add an interface to load ldiskfs block bitmaps&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-10946&quot;&gt;&lt;del&gt;LU-10946&lt;/del&gt;&lt;/a&gt; : add an interface to load ldiskfs block bitmaps&lt;/p&gt;</comment>
                            <comment id="226959" author="pjones" created="Mon, 30 Apr 2018 17:35:34 +0000"  >&lt;p&gt;Nathan&lt;/p&gt;

&lt;p&gt;Thanks for opening this ticket. It will be good to get a variety of views onto possible approaches here.&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="226978" author="adilger" created="Mon, 30 Apr 2018 21:20:14 +0000"  >&lt;p&gt;The proposal for &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-10946&quot; title=&quot;add an interface to load ldiskfs block bitmaps&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-10946&quot;&gt;&lt;del&gt;LU-10946&lt;/del&gt;&lt;/a&gt; to pin the block and inode bitmaps would also help for the MDS, though to a lesser extent because the MDT is typically flash so reading them on demand from storage will be much faster than competing with a streaming I/O workload on the OST on spinning disks.&lt;/p&gt;

&lt;p&gt;The block bitmaps would need 4KB of RAM per 128MB of MDT space, and the inode bitmaps would double that.  For a largish MDTs, say 8TB (=4B files), this would mean 4KB * (8TB/128MB) = 256MB for the block bitmaps, and an additional 256MB for the inode bitmaps, which is not unreasonable.  Pinning the inode &lt;b&gt;tables&lt;/b&gt; on the MDT would be totally impractical, since they consume (by default) 1/2 of all the MDT space (i.e. you would need 4TB of RAM to pin all of the MDT inode tables).&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="10112">LU-15</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="19985">LU-3631</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="15873">LU-1885</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="51954">LU-10946</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </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|hzzwiv:</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>