[YANGTOOLS-1065] Minimize EffectiveStatement implementation footprint Created: 11/Jan/20 Updated: 28/Oct/20 Resolved: 06/Oct/20 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | parser |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0 |
| Type: | Improvement | 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 | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Epic Link: | Parser Performance | ||||||||||||||||||||||||
| Description |
|
Heap dump analysis from YANGTOOLS-652 is showing that our effective statements are needlessly big, as their fields end up having default values stored. This comes from the way classes are modeled and can be alleviated by splitting implementations based on what they actually declare. |
| Comments |
| Comment by Robert Varga [ 22/Sep/20 ] |
|
The only remaining classes are UnknownStatements, which need another pass with API-incompatible changes. |