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/NETCONF-571 netconf <p>Running scale test of connected 10K instances, we end up consuming 1.2GB heap, which boils down to around ~125kB per session overhead.</p> <p>Drilling down into this, it looks like we are retaining a 32KiB HeapByteBuffer in each session – i.e. 25%, through a read timeout task. Investigate the root cause for this, potentially switching to netty provider instead of nio2.</p> NETCONF-571

Rework SSHD integration

Improvement Medium Confirmed Unresolved Unassigned Robert Varga Mon, 1 Oct 2018 14:29:04 +0000 Mon, 31 Jul 2023 19:16:31 +0000 7.0.0 netconf 0 2 <p>This seems to be related AsyncSshHandler's use of SshClient – which really is the bridge between sshd-core and netty.</p> <p>In order to eliminate this buffer, we really need to thoroughly rework SSH integration, because the "netconf" SSH subsystem needs to be acting as an io.netty.channel.Channel, with the rest of the processing tied in as handler.</p> <p>This in turn requires that TLS/TCP sessions are established differently (directly via Netty) than SSH sessions (established when netconf subsystem is opened) – which means we need to kill the protocol framework.</p> <p>This is a misleading comment. <a href="https://jira.opendaylight.org/browse/NETCONF-674" title="Eliminate use of AsyncSshHandlerReader" class="issue-link" data-issue-key="NETCONF-674"><del>NETCONF-674</del></a> deals with that.</p> <p>The source of the HeapByteBuffer is actually NIO2 used by Mina. </p> Blocks NETCONF-590 NETCONF-674 NETCONF-699 NETCONF-1069 NETCONF-1070 Development Rank 0|i03j3j: