[YANGTOOLS-428] InMemoryDataTreeCandidate getModificationType speedup Created: 19/Mar/15  Updated: 10/Apr/22  Resolved: 30/Mar/15

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

Type: Improvement
Reporter: Robert Varga Assignee: Robert Varga
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


 Description   

The internal (logical) and external (physical) transitions are calculated on-demand when a client requests it. Determining how a MERGE maps onto WRITE/SUBTREE_MODIFIED can take up to 4 instanceof checks.

It seems this field can be cached in the ModifiedNode when SchemaAwareApplyOperation runs, so that we do not have to perform any additional analysis.

 Comments   
Comment by Robert Varga [ 22/Mar/15 ]

https://git.opendaylight.org/gerrit/16957 (infra and hooks)
https://git.opendaylight.org/gerrit/16966 (switch to using pre-computed value)
https://git.opendaylight.org/gerrit/16967 (non-tradeoff improvement to accuracy)
https://git.opendaylight.org/gerrit/16968 (unmodified subtree pruning with small penalty)

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