<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:55:48 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>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[CONTROLLER-1542] Performance for MD-SAL data store Deletes reduced 100x in Boron</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-1542</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;There has been a significant performance regression for MD-SAL Deletes between Beryllium and Boron. Please see the attached document that compares data store performance between Beryllium and Boron using the dsbenchmark tests.&lt;/p&gt;

&lt;p&gt;Performance for Deletes in Boron should be in the same ballpark as in Beryllium.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="26096">CONTROLLER-1542</key>
            <summary>Performance for MD-SAL data store Deletes reduced 100x in Boron</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/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="green"/>
                                    <resolution id="10003">Cannot Reproduce</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="jmedved@cisco.com">Jan Medved</reporter>
                        <labels>
                    </labels>
                <created>Mon, 29 Aug 2016 16:56:21 +0000</created>
                <updated>Tue, 25 Jul 2023 08:24:12 +0000</updated>
                            <resolved>Wed, 31 Aug 2016 09:30:20 +0000</resolved>
                                                                    <component>mdsal</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="51493" author="jmedved@cisco.com" created="Mon, 29 Aug 2016 16:56:21 +0000"  >&lt;p&gt;Attachment Data Store Performance Test.docx has been added with description: Boron MD-SAL Data Store performance report&lt;/p&gt;</comment>
                            <comment id="51490" author="vrpolak" created="Tue, 30 Aug 2016 14:09:52 +0000"  >&lt;p&gt;Current graphs do not show significant difference between Boron &lt;span class=&quot;error&quot;&gt;&amp;#91;0&amp;#93;&lt;/span&gt; and Beryllium &lt;span class=&quot;error&quot;&gt;&amp;#91;1&amp;#93;&lt;/span&gt; snapshots. I will run released Beryllium in Sandbox to see if the performance is different there.&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;0&amp;#93;&lt;/span&gt; &lt;a href=&quot;https://jenkins.opendaylight.org/releng/view/controller/job/controller-csit-1node-periodic-benchmark-only-boron/plot/getPlot?index=0&amp;amp;width=750&amp;amp;height=1000&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opendaylight.org/releng/view/controller/job/controller-csit-1node-periodic-benchmark-only-boron/plot/getPlot?index=0&amp;amp;width=750&amp;amp;height=1000&lt;/a&gt;&lt;br/&gt;
&lt;span class=&quot;error&quot;&gt;&amp;#91;1&amp;#93;&lt;/span&gt; &lt;a href=&quot;https://jenkins.opendaylight.org/releng/view/controller/job/controller-csit-1node-periodic-benchmark-only-beryllium/plot/getPlot?index=0&amp;amp;width=750&amp;amp;height=1000&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opendaylight.org/releng/view/controller/job/controller-csit-1node-periodic-benchmark-only-beryllium/plot/getPlot?index=0&amp;amp;width=750&amp;amp;height=1000&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="51491" author="vrpolak" created="Tue, 30 Aug 2016 15:57:01 +0000"  >&lt;p&gt;The benchmark job produces two pictures. One is &quot;Performance by structure&quot;, the other one is &quot;Performance by operations&quot; (not sure how the two definitions differ).&lt;br/&gt;
Sandbox runs (Beryllium snapshot and Beryllium the original release) do not differ significantly &lt;span class=&quot;error&quot;&gt;&amp;#91;0&amp;#93;&lt;/span&gt; (per structure), &lt;span class=&quot;error&quot;&gt;&amp;#91;1&amp;#93;&lt;/span&gt; (per operations).&lt;/p&gt;

&lt;p&gt;Is it possible that the alleged 100x decrease was caused by comparing the two different pictures?&lt;/p&gt;

&lt;p&gt;Keeping this unconfirmed for now.&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;0&amp;#93;&lt;/span&gt; &lt;a href=&quot;https://jenkins.opendaylight.org/sandbox/job/controller-csit-1node-periodic-benchmark-only-beryllium/plot/getPlot?index=1&amp;amp;width=750&amp;amp;height=1000&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opendaylight.org/sandbox/job/controller-csit-1node-periodic-benchmark-only-beryllium/plot/getPlot?index=1&amp;amp;width=750&amp;amp;height=1000&lt;/a&gt;&lt;br/&gt;
&lt;span class=&quot;error&quot;&gt;&amp;#91;1&amp;#93;&lt;/span&gt; &lt;a href=&quot;https://jenkins.opendaylight.org/sandbox/job/controller-csit-1node-periodic-benchmark-only-beryllium/plot/getPlot?index=0&amp;amp;width=750&amp;amp;height=1000&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opendaylight.org/sandbox/job/controller-csit-1node-periodic-benchmark-only-beryllium/plot/getPlot?index=0&amp;amp;width=750&amp;amp;height=1000&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="51492" author="vrpolak" created="Wed, 31 Aug 2016 09:30:20 +0000"  >&lt;p&gt;This close to release (and release review), it is not desired to have a Bug which is both blocker and unconfirmed.&lt;/p&gt;

&lt;p&gt;Setting to WORKSFORME, but please re-open this as soon as additional hints of a real bug appear.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="13586" name="Data Store Performance Test.docx" size="202837" author="jmedved@cisco.com" created="Mon, 29 Aug 2016 16:56:21 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>6571</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=6571]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10206" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Issue Type</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10300"><![CDATA[Bug]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i02r7r:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>