Hi,

Can you clarify why you want them without history? In short that is not possible.
For nodes other than Constant Value Type simulation the history is also simulated on-demand, it doesn’t take memory. For Constant nodes (yes the name is maybe not ideal) it does store some amount of the real values if written by a client.

That being said, there is no easy way to add 200k nodes. It should be noted that you most likely end up having performance problems long before reaching that point, but depending on the machine and patience one way to try is having the Pro license and loading a nodeset with that many nodes.

Other than that there is an option in the right-click menu to duplicate a node, though that is intentionally limited to 4999 due to performance constraints. Though, you can add duplicate node inside a folder, and then duplicate the folder itself, possibly also cut-pasting the folder as a subfolder and continue.

Please note that saving the project can take a _very_ long time with higher node counts depending on the machine.

I think at the moment the only way would be to load a nodeset with all the nodes and having AccessLevel=”1″ for them to indicate only CurrentRead. However simulating or making duplicates of those does change the accesslevel attributes.

Maybe we can some day add a flag when creating the node or provide additional attribute simulation or configurability, though not sure when or if this happens (you would need to talk with sales@prosysopc.com)

So if having static data would be enough then that loading via a nodeset is a workaround, though loading such amount of nodes could take hours depending on the distribution of types and instances etc. (in short inside the SDK if ‘UaNodes’ are being used then adding a new reference does check all references of that node first, types do have a reference to the instances of them). This would require creating such nodesets though. We have some future stuff https://prosysopc.com/blog/pla…..on-server/, that might make it easier to try to duplicate a server (though exporting this amount of nodes might be hard, memory might run out first). Also I should note that the playback feature itself most likely cannot scale to a very high node count. Anyway, if you wish to test, ask sales@prosysopc.com.

However, since you do have the SDK, it might be just easier to try to build something on top of the SampleConsoleServer. For node amounts of this many I would recommend going with the ‘MyBigNodeManager’ example route, though it should be noted that instances and references here must be modelled manually (i.e. it is more like a view to some existing data(base)).