Updating from Python-opcua to Opcua-asyncio #1818
Replies: 3 comments
-
none of them is good for highspeed. In theory the async version can be a bit faster since you have better control over what is happening when |
Beta Was this translation helpful? Give feedback.
-
For most use cases the speed is determined by the network (latency, amount network request needed for a operation). With asyncua you could do multiple request in parallel, so there you could gain some performance, depending on your use case. The real advantage of asyncua is that support it support more OPC UA features, the spec compatibility and more bugfixes missing in the old version. |
Beta Was this translation helpful? Give feedback.
-
hello again and first of all, thank you for your comments. Currently, I have been using the old version for more than 4 years and the performance obtained is more than satisfactory as I am able to read 1 single 4k structure in a averatge time of 10ms. My doubt to change to asyncio is precisely because of the evolution of the spec and support for new features of the standard. I also plan to add 2 or 3 more structures with trivial data that I will not have to read at such high speed (for example 30 sec) and asynchronous. that's why i plan to migrate my code to the new version. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello all ...
I've been using Python- opcua for years now that it's already deprecated.
I have decided that it is time to start the most current Opcua- asyncio but my doubt is as follows.
I'm currently reading from a PLC a data structure (bool, int, dint...) of 4096 Bytes at a speed of approximately 10 ms.
Using the actual asynx module will I be able to get the same performance?
What advantages does Opcua-asyncio have to use with respect to python- opcua if I want to follow the same high-speed synchronized reading strategy?
Thank you very much.
Beta Was this translation helpful? Give feedback.
All reactions