https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/MDSAL-443 mdsal <p>The LazyDataObject-&gt;CodecDataObject refactor allows us to improve the dispatch performance as we are no longer bound by InvocationHandler API. First part of this was already done in <a href="https://jira.opendaylight.org/browse/MDSAL-442" title="Teach binding-dom-codec to keep its proxies in a separate ClassLoader" class="issue-link" data-issue-key="MDSAL-442"><del>MDSAL-442</del></a>, where we are using simple integers to lookup NodeContextSupplier which handles decoding of NormalizedNode data – ditching a Map in favor of simple array.</p> <p>As it turns out, though, we can do a bit better here, as CodecDataObject only needs that lookup from DataObjectCodecContext. Since the offsets are fixed anyway, we may as well generate constant fields in the CodecDataObject overlay and pass them down to CodecDataObject proper, which will then just use the constant.</p> <p>This will eliminate all lookups from the hot path and use easily propagated constants instead. It will also save one field in CodecDataObject, as it will no longer require a reference to DataObjectCodecContext.</p> MDSAL-443

Inline CodecDataObject's NodeContextSuppliers

Improvement Medium Confirmed Unresolved Unassigned Robert Varga pt Tue, 23 Apr 2019 08:02:39 +0000 Tue, 9 Jan 2024 09:06:20 +0000 14.0.0 Binding runtime 0 1 <p>The disconnect of CodecDataObject is not complete, as we still need the DataObjectCodecContext reference for AugmentableCodecDataObject mechanics. In order to eliminate that dependency will need <a href="https://jira.opendaylight.org/browse/MDSAL-392" title="Clean up BindingRuntimeContext instantiation" class="issue-link" data-issue-key="MDSAL-392"><del>MDSAL-392</del></a>, i.e. full visibility into all possible augmentations and their ClassLoaders. This issue will deal only with normal fields and the key() method.</p> <p>This optimization is not valid, as it breaks the ability to transport groupings: if a grouping is used somewhere we need to rehost the NodeContextSupplier.</p> <p>Hence we need to dial this optimization down, so that we understand whether a node is defined within the context of a grouping – in which case we need to fall back to name-based lookups. If a node is defined outside of a grouping, i.e. it cannot be reused, we are free to perform this optimization.</p> <p>This will require some amount of refactoring to have DataObjectCodecContext the appropriate hooks to support such duality of operation.</p> <p>We have everything we need in CodecDataObjectGenerator.Fixed, but we also need instantiation information from <a href="https://jira.opendaylight.org/browse/MDSAL-669" title="Retain grouping/uses instantiation vectors" class="issue-link" data-issue-key="MDSAL-669"><del>MDSAL-669</del></a>.</p> Blocks MDSAL-444 MDSAL-442 MDSAL-669 Development Rank 0|i03njb: