<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:16:10 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>[NETCONF-889] Improve EOM aggregator performance</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-889</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;The decoding performance of&#160;DelimiterBasedFrameDecoder, and hence the performance of NetconfEOMAggregator extending&#160;DelimiterBasedFrameDecoder becomes the bottleneck of NETCONF channel pipeline when small increments of a long frame are processed. For example, fetching YANG schema files (total 22 MB) from Juniper MX2020 takes about 16 minutes.&lt;/p&gt;

&lt;p&gt;The main reason for this poor performance is because &lt;a href=&quot;https://github.com/netty/netty/blob/4.1/codec/src/main/java/io/netty/handler/codec/DelimiterBasedFrameDecoder.java#L314&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;delimiter search starts over from the beginning of the frame (readerIndex)&lt;/a&gt; for each decode call in the indexOf method.&lt;/p&gt;</description>
                <environment></environment>
        <key id="36005">NETCONF-889</key>
            <summary>Improve EOM aggregator performance</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="2" iconUrl="https://jira.opendaylight.org/images/icons/priorities/critical.svg">High</priority>
                        <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="10000">Done</resolution>
                                        <assignee username="sangwookha">Sangwook Ha</assignee>
                                    <reporter username="sangwookha">Sangwook Ha</reporter>
                        <labels>
                    </labels>
                <created>Mon, 11 Jul 2022 18:06:23 +0000</created>
                <updated>Mon, 31 Oct 2022 12:44:32 +0000</updated>
                            <resolved>Fri, 29 Jul 2022 10:42:40 +0000</resolved>
                                                    <fixVersion>4.0.0</fixVersion>
                    <fixVersion>3.0.6</fixVersion>
                    <fixVersion>2.0.17</fixVersion>
                                    <component>netconf</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="71311" author="rovarga" created="Tue, 12 Jul 2022 15:06:11 +0000"  >&lt;p&gt;So there is a pre-existing patch for this.&lt;/p&gt;

&lt;p&gt;I also wonder if it would not make sense to also push a fix for Netty.&lt;/p&gt;</comment>
                            <comment id="71312" author="JIRAUSER13318" created="Tue, 12 Jul 2022 15:58:02 +0000"  >&lt;p&gt;Right, I found that out after submitting a change. The idea is the same, just difference in keeping track of progress.&lt;br/&gt;
One thing I wonder, for both changes, is whether it&apos;s robust enough to handle change in ByteBuf allocation, which I think should happen in one way or another because the index cannot increase forever.&lt;/p&gt;</comment>
                            <comment id="71313" author="JIRAUSER13318" created="Tue, 12 Jul 2022 20:41:23 +0000"  >&lt;p&gt;There was an issue with change 75490 as suspected - it fails to process a case where ByteBuf is updated with readerIndex reset to 0.&lt;br/&gt;
I fixed the issue and pushed a &lt;a href=&quot;https://git.opendaylight.org/gerrit/c/netconf/+/75490/5&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;new patch set&lt;/a&gt; with another test case and some cleanup.&lt;br/&gt;
&lt;a href=&quot;https://jira.opendaylight.org/secure/ViewProfile.jspa?name=rovarga&quot; class=&quot;user-hover&quot; rel=&quot;rovarga&quot;&gt;rovarga&lt;/a&gt;, please take a look.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </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_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i042mv:</customfieldvalue>

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