[NETCONF-480] GET on /apidoc/apis takes long time to respond Created: 25/Oct/17  Updated: 27/Jul/23  Resolved: 27/Jul/23

Status: Resolved
Project: netconf
Component/s: restconf-openapi
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: High
Reporter: Vratko Polak Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: pt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates NETCONF-938 Cannot generate API docs for Junos de... In Review

 Description   

Originally other symptom was described in NETCONF-473.

In local tests, generating apidocs took around 1 second just for network-topology model.

Nitrogen has less restconf apis than Carbon, but Carbon frequently responds withing 15 seconds, so this is a performance regression.
Perhaps from Yangtools?

 Comments   
Comment by Vratko Polak [ 26/Oct/17 ]

The only notable difference between Carbon and Nitrogen I have found is the conversion from org.json to Jackson done in [0].

[0] https://git.opendaylight.org/gerrit/58839

Comment by Robert Varga [ 19/Aug/22 ]

Yeah I have noticed the implementation.
Throwing it against JunOS models will probably show that the load times are just abysmal and that may to a re-implementation.

We really need to see some benchmark results from such an enterprise – first load times, then some YourKit traces as to what is going on.

Comment by Robert Varga [ 27/Jul/23 ]

NETCONF-938 leads the effort to get this in order.

Generated at Wed Feb 07 20:15:08 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.