[YANGTOOLS-1066] SchemaPath identification of SchemaNodes is costly and useless Created: 11/Jan/20  Updated: 13/Oct/21  Resolved: 02/Sep/21

Status: Resolved
Project: yangtools
Component/s: parser
Affects Version/s: None
Fix Version/s: 8.0.0

Type: Epic Priority: Medium
Reporter: Robert Varga Assignee: Robert Varga
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File yt601_junos.png    
Issue Links:
Blocks
blocks YANGTOOLS-912 {Input,Output}Statement definition vi... Resolved
blocks YANGTOOLS-1067 Use flyweight EffectiveStatement impl... Resolved
blocks YANGTOOLS-1236 Remove yang.model.api.SchemaPath Resolved
blocks YANGTOOLS-1316 Re-examine argument storage in effect... Resolved
blocks YANGTOOLS-652 Improve YANG parser performance and f... Confirmed
Relates
relates to YANGTOOLS-694 Eliminate duplicate DescriptionEffect... Resolved
relates to MDSAL-694 VerifyException thrown when resolving... Resolved
Epic Name: Get rid of SchemaNode.getPath()

 Description   

Based on heap dump analysis of YANGTOOLS-652, SchemaPath instances are taking up 11% (13% with partial YANGTOOLS-1065) of retained heap size.

The problem is that SchemaPath is used in quite a few places to provide type inference and we do not have a replacement mechanism.

Hence we first need to add that mechanism, then deprecate/migrate SchemaPath usage and finally kill the ill notion of a SchemaPath.

 Comments   
Comment by Robert Varga [ 11/Jan/20 ]

YANGTOOLS-694 deals with reducing number of contexts and once it's done this issue starts blocking further progress.

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