Hi there.
I'm developing a manager using the C# API. This is working nicely (and much easier compared to using the C++ API). However. I found that certain functions are slower than expected.
Example:
* I tried with '-rcv 2' and see that my manager receives the dp container
* still, a function like 'dpTypeName = dataModel.GetDpTypeNameOfDp(dp.Dp );' is relatively slow ?
Does anyone have an explanation.
Can someone explain my why these functions all have an 'async' version. ( like GetDpTypeNameOfDpAsync() ). I would expect the manager to have the dp container in-memory. Why would you need an async version of these functions ?
hope ayone has an answer
Share the fun
Frenk Mulder
Why is the C# API 'slow'
Search
Re: Why is the C# API 'slow'
All C# functions are only C++ wrappers. All the wrappers cost more time in execution.
When you call the function GetDpTypeNameOfDp(dpName), internally GetDpTypeNameOfDpAsync(dpName).GetAwaiter().GetResult(); is called.
When you call the function GetDpTypeNameOfDp(dpName), internally GetDpTypeNameOfDpAsync(dpName).GetAwaiter().GetResult(); is called.
Re: Why is the C# API 'slow'
The whole API is by design asynchronous.
Also information coming from DP-Identification is asynchronous implemented.
The synchronous methods are just synchronized versions of the asynchronous.
I recommend to use always the asynchronous!.
The asynchronous style of implementation has the big benefit, that it can be used in multithreaded environment.
In common the C# API is thread-safe in sense of calling API methods. The synchronization of the response is in the responsibility of usage code.
The inner communication with EVENT is solved in own thread.
Regarding performance:
What is faster depends on what are you comparing.
If you compare a multithreaded access in C# with a single threaded access in C++ for a single method it is impossible that C# is as fast as C++.
For a single operation C# is on top of C++ it can't be faster.
If your application has to do much things in parallel and have to deal with a lot of data, then the multithreading possibilities of C# API can be faster.
But also that depends on the implementation.
I think the big benefit of C# API, compared to C++ API, is the much easier usage and the possibility to use in multithreaded applications with the help of the big .NET extension package universe.
Also information coming from DP-Identification is asynchronous implemented.
The synchronous methods are just synchronized versions of the asynchronous.
I recommend to use always the asynchronous!.
The asynchronous style of implementation has the big benefit, that it can be used in multithreaded environment.
In common the C# API is thread-safe in sense of calling API methods. The synchronization of the response is in the responsibility of usage code.
The inner communication with EVENT is solved in own thread.
Regarding performance:
What is faster depends on what are you comparing.
If you compare a multithreaded access in C# with a single threaded access in C++ for a single method it is impossible that C# is as fast as C++.
For a single operation C# is on top of C++ it can't be faster.
If your application has to do much things in parallel and have to deal with a lot of data, then the multithreading possibilities of C# API can be faster.
But also that depends on the implementation.
I think the big benefit of C# API, compared to C++ API, is the much easier usage and the possibility to use in multithreaded applications with the help of the big .NET extension package universe.