5) No I never modified that property

6) I'm running a couple of tests where in one there are no subscriptions and another one where I subscribe to the variables. In the application I have subscribed variables during the whole life cycle of the application. Those variables belongs to different clients tho. And I don't know if it matters or not but some of the clients I create don't have subscribed variables.

Regards

1) The server is on the same computer

2) All recurrent operations are with a refresh interval shorter than a second.
Eventually when the operator change a parameter the application will write that value to the OPC server.

3) I found a bug in my test code and I'm actually rerunning the test. I will post the results in a few hours.

4) I'm sorry, my fault. In my code I do not call the subscription method if that number is below 100(ms) and it is the number I pass to client_.SubscribeItem(...);


The problem is that the write function often take a few seconds to complete.

Thanks

Hi, we're having some performances issues on our application.

It happens that sometimes the OPC client take very long time (even some seconds) to read a value.

We have a lot of parameters (~2000) that are written in block once the application starts and then written again when the operator change a parameter's value but in this case only that specific parameter.

We have a few hundreds of other variables that are read constantly and an hundred of other variables that are written constantly.

Can the large amount of variables affect the overall performances?

We are using multiple instances of the EasyDAClient, one for the parameters (all of them with refresh rate = -1 and no subscription) and various for the I/O variables (with various refresh rates and some subscriptions depending on the function of the variable).

Can you tell us if this is the right way or if there is a better solution to our problem?

Any suggestion is appreciated, thanks