1 of 1 people found this helpful
I suspect your PI SDK timing was for the time it took to hand off the data to the PI Buffer Subsystem.
You could use OSIsoft.AF.PI.PIPoint.UpdateValues() rather than AFListData, and enable PI Buffer Subsystem (specify you want to buffer in the overload for UpdateValues).
As Rhys mentioned, the difference may be due to buffering. You can specify the AFBufferOption in the UpdateValues call.
To avoid some overhead with AFListData.UpdateValues, you can also use PIServer.UpdateValues Method for multiple PIPoints and again make sure buffering is used.
We're looking into a natively async UpdateValues in the future but it remains to be seen what the performance improvements could be.
Thanks Rhys. When I switched on the buffer option the times of the AFSDK method are very similar to the PISDK calls.
I can happily continue with just the AFSDK now.
This is good that you could solve this issue!
May I ask you to mark the correct answer?
Have a good day!