Hi Team, I am doing the latency analysis of one data feed in our TREP env. The way i handle it is:
First, I run " ./rmdstestclient -S Source -h hostname -p 14002 -f /reuters/ads/demo/latency.ric -o 500 -ct rssl -t 2 -X -d 3 -m > output &"
Then I calculate the time difference between the data received time and the "BID_TIME" and use the result as the update latency for one ticker update.
My question is: is this the correct way to monitor/calculate the tick update latency? Coz what I notice is: even sometime the rmdstestclient results shows there is delay (~ 2 to 5 sed), our downstream application doesn't report any delay. Is it possible that the rmdstestclient itself will introduce some latency due to the server read/write capability or server resource capability?
If rmdstestclient is not the right tool to get the latency detail, what will be the correct tool I should us? or is there any parameter in the rmdstestclient command or system variable that i can tune to get a better performance?
If rmdstestclient is not the right tool, would you please help to advise what tool I should use to achieve my purpose?