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.
- blocks
-
YANGTOOLS-912 {Input,Output}Statement definition violates ModelStatement API contract
- Resolved
-
YANGTOOLS-1067 Use flyweight EffectiveStatement implementations
- Resolved
-
YANGTOOLS-1236 Remove yang.model.api.SchemaPath
- Resolved
-
YANGTOOLS-1316 Re-examine argument storage in effective statements
- Resolved
-
YANGTOOLS-652 Improve YANG parser performance and footprint
- Confirmed
- relates to
-
YANGTOOLS-694 Eliminate duplicate DescriptionEffectiveStatementImpl objects
- Resolved
-
MDSAL-694 VerifyException thrown when resolving leafrefs with TAPI models
- Resolved