<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:23:45 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-2264] Create scripts that create &quot;noise&quot; for testing on Hyperion</title>
                <link>https://jira.whamcloud.com/browse/LU-2264</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Create scripts that generate noise while testing on Hyperion.&lt;/p&gt;</description>
                <environment></environment>
        <key id="16551">LU-2264</key>
            <summary>Create scripts that create &quot;noise&quot; for testing on Hyperion</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="2">Won&apos;t Fix</resolution>
                                        <assignee username="wc-triage">WC Triage</assignee>
                                    <reporter username="jlevi">Jodi Levi</reporter>
                        <labels>
                    </labels>
                <created>Fri, 2 Nov 2012 17:37:45 +0000</created>
                <updated>Tue, 25 Apr 2023 21:04:40 +0000</updated>
                            <resolved>Tue, 25 Apr 2023 21:04:40 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                            <comments>
                            <comment id="47335" author="keith" created="Fri, 2 Nov 2012 18:33:20 +0000"  >&lt;p&gt;In general the goal is to have some background stress scripts in the tests.  &lt;/p&gt;

&lt;p&gt;The three main scripts will be:&lt;/p&gt;

&lt;p&gt;1. Memory. We want to carefully create a near oom situation. The rational is that allocations can block and we want to be sure the code can deal with this.  We also want to be sure that Lustre and the Linux VM play well together when resources become tight. &lt;/p&gt;

&lt;p&gt;2. Cpu load.  Create fake cpu loads to simulate unstable client processing. There will be a random mode that will use cpu_affinity. &lt;/p&gt;

&lt;p&gt;Both of these items are not Hyperion specific but rather a form of general stress testing.   &lt;/p&gt;

&lt;p&gt;3.  Cpu throttling. A 3rd hardware specific test will be cerated that will change CPU power states randomly. This will cause cpu latency/ jitter.  Having the cpu change power states blocks all processing on it for a brief period of time.  This sort of testing can only run on real hardware, but VM&apos;s have their own forms of jitter.   &lt;/p&gt;
</comment>
                            <comment id="48051" author="keith" created="Tue, 20 Nov 2012 00:51:21 +0000"  >&lt;p&gt;&lt;a href=&quot;http://review.whamcloud.com/4619&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/4619&lt;/a&gt; contains code out for comment on the first two items.   There is a larger issue about how we want to integrate this code for use.  For now the code is fortestonly for review as there is no calls to use the new code.&lt;/p&gt;</comment>
                            <comment id="50559" author="keith" created="Wed, 16 Jan 2013 13:43:51 +0000"  >&lt;p&gt;I have split the code into 2 parts. &lt;/p&gt;

&lt;p&gt;For memhog.c changes: &lt;a href=&quot;http://review.whamcloud.com/4619&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/4619&lt;/a&gt; &lt;br/&gt;
For processor.sh:     &lt;a href=&quot;http://review.whamcloud.com/5041&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/5041&lt;/a&gt;&lt;/p&gt;
</comment>
                    </comments>
                    <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|hzvbk7:</customfieldvalue>

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