https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETCONF-480 netconf <p>Originally other symptom was described in <a href="https://jira.opendaylight.org/browse/NETCONF-473" title="Apidoc: multiple &quot;Could not generate doc&quot; warnings" class="issue-link" data-issue-key="NETCONF-473"><del>NETCONF-473</del></a>.</p> <p>In local tests, generating apidocs took around 1 second just for network-topology model.</p> <p>Nitrogen has less restconf apis than Carbon, but Carbon frequently responds withing 15 seconds, so this is a performance regression.<br/> Perhaps from Yangtools?</p> NETCONF-480

GET on /apidoc/apis takes long time to respond

Improvement High Resolved Duplicate Unassigned Vratko Polak pt Wed, 25 Oct 2017 12:52:39 +0000 Thu, 27 Jul 2023 19:51:37 +0000 Thu, 27 Jul 2023 19:50:58 +0000 restconf-openapi 0 1 <p>The only notable difference between Carbon and Nitrogen I have found is the conversion from org.json to Jackson done in <span class="error">&#91;0&#93;</span>.</p> <p><span class="error">&#91;0&#93;</span> <a href="https://git.opendaylight.org/gerrit/58839" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/58839</a></p> <p>Yeah I have noticed the implementation.<br/> Throwing it against JunOS models will probably show that the load times are just abysmal and that may to a re-implementation.</p> <p>We really need to see some benchmark results from such an enterprise &#8211; first load times, then some YourKit traces as to what is going on.</p> <p><a href="https://jira.opendaylight.org/browse/NETCONF-938" title="Cannot generate API docs for Junos device" class="issue-link" data-issue-key="NETCONF-938">NETCONF-938</a> leads the effort to get this in order.</p> Duplicate NETCONF-938 Development Rank 0|i036u7: