[CONTROLLER-649] Performance: BindingToNormalizedNodeCodec must not use intermediate representation Created: 25/Jul/14  Updated: 22/Aug/14  Due: 07/Aug/14  Resolved: 22/Aug/14

Status: Resolved
Project: controller
Component/s: mdsal
Affects Version/s: Helium
Fix Version/s: None

Type: Bug
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


External issue ID: 1425

 Description   

As evidenced here:

public Entry<org.opendaylight.yangtools.yang.data.api.InstanceIdentifier, NormalizedNode<?, ?>> toNormalizedNode(
final Entry<org.opendaylight.yangtools.yang.binding.InstanceIdentifier<? extends DataObject>, DataObject> binding) {
Entry<org.opendaylight.yangtools.yang.data.api.InstanceIdentifier, CompositeNode> legacyEntry = bindingToLegacy
.toDataDom(binding);
Entry<org.opendaylight.yangtools.yang.data.api.InstanceIdentifier, NormalizedNode<?, ?>> normalizedEntry = legacyToNormalized
.toNormalized(legacyEntry);
LOG.trace("Serialization of {}, Legacy Representation: {}, Normalized Representation: {}", binding,
legacyEntry, normalizedEntry);
if (isAugmentation(binding.getKey().getTargetType())) {

the translation uses intermediate representation in CompositeNode, since this is performance-critical path, this has to be avoided.



 Comments   
Comment by Tony Tkacik [ 08/Aug/14 ]

https://git.opendaylight.org/gerrit/#/c/9757/

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