Hello!

In our OPC UA server Implementation, we have implemented our own “TandemNodeManager” which is extended by the NodeManagerUaNode.

In the constructor, we only have the super() call.
In the @Override method init(), there is a super.init() followed by createAddressSpace(), which then contains our own code.

In the OPC UA server, the certificates are loaded last in initialize(), and then the custom NodeManager is instantiated.
That’s all from your code examples.

We didn’t notice anything unusual under Windows during development.
However, when we run the implementation on our hardware platform, I see the following log entries:

07:32:20.091 INFO [main] c.prosysopc.ua.ApplicationIdentity | Reading application certificate from /usr/local/***_2048.der
07:32:20.103 INFO [main] c.prosysopc.ua.ApplicationIdentity | Reading private key from keystore /usr/local/***_2048.pem
07:32:25.836 INFO [main] c.p.ua.server.NodeManagerRoot | Loading information model jar:file:/var/lib/***/prosys-opc-ua-sdk-client-server-5.2.2-139.jar!/com/prosysopc/ua/types/opcua/server/Opc.Ua.NodeSet2.xml
07:32:51.498 INFO [main] c.p.ua.server.NodeManagerRoot | Loaded: ModelInfo [namespace=http://opcfoundation.org/UA/, version=1.05.03, publicationDate=12/15/23 00:00:00.0000000 GMT, dependencies=[]]

After that, the first log entry from the createAddressSpace() follows:
07:33:16.217 INFO [main] c.m.h.o.opcserver.TandemNodeManager | [..] createAddressSpace

So we need > 50 seconds for this section. Of that, ~26 seconds are for loading the Opc.Ua.NodeSet2.xml.
It is known that our hardware platform is inefficient when processing XML files.

Is there a way to speed this up?
And what else is done after the XML has been loaded, which explains the remaining ~25 seconds?

Thank you for your help!