I know it's possible to add some kind of instrumentation to a sensor, to show the values of the parameters when it's being called.
I am currently having issues with a socketRead0 where it's taking to much time. Besides retrieving the parameters values, what other approach may I use to find out what is the root cause?
Best regards,
Answer by Joe H. ·
I would investigate what is at the other end of that socket call. You can capture the IP address of the other end which might help (if you don't already know).
I would also verify that it's blocked on the read, as opposed to a busy loop constantly processing nuggets. Are there lots of calls to the socket.Read, or lots of time on a single call? Is the chunk size of data perhaps too small and many small reads are happening, or is it simply blocked waiting on the other end to respond?
JANUARY 15, 3:00 PM GMT / 10:00 AM ET