You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On our machine we have around 6-8 OPC UA servers installed that register with the LDS every 30 seconds. This results in a rather high CPU usage (LDS is the process with the most CPU usage on the whole machine):
@MD-V : At this point, there are no plans for any performance improvements (1% CPU is not critical). Other than the periodical OPC-UA Server registration, the LDS is also communicating with other LDS instances on the local network (via Bonjour/Avahi), so it is normal for it to have a higher load that the .Net based implementation.
@erhardgrishaber Okay, 1% doesn't seem critical but in the context that the LDS uses the most CPU overall (even more than our main control applications) means many wasted CPU cycles (for simple discovery functionality).
On our machine we have around 6-8 OPC UA servers installed that register with the LDS every 30 seconds. This results in a rather high CPU usage (LDS is the process with the most CPU usage on the whole machine):

I have installed a prototype of my .NET based LDS (https://github.com/MD-V/LightLDSCore) on the machine.

It uses much less CPU (see image):
Is there any way to optimize the CPU usage for the UA-LDS?
The text was updated successfully, but these errors were encountered: