[This message was posted by Aditya Khandekar of Merrill Lynch 
<[email protected]> to the "General Q/A" discussion forum at 
http://fixprotocol.org/discuss/22. You can reply to it on-line at 
http://fixprotocol.org/discuss/read/950fe180 - PLEASE DO NOT REPLY BY MAIL.]

> Latency can mean several things, as stated above. I think the three
> most relevant figures are -One way: Time it takes from the source to
> the destination. Which is in fact very hard to get unless you control
> both ends. -Round trip, which is an end to end latency between an
> order was sent and the acknowledgment was received. Doesn't work for
> one way messenging (like market data). -Hop to hop: the time it takes
> for a message to travel through a specific set of software and
> hardware routers.
> 
> This can be done at the software level (aka looking at time stamps or
> log times), or at the network level (packet timestamps). Although
> software is the easiest approach, it has several inherent flaws. Indeed,
> what you are seeing in a log is the time the software understood the
> message and printed the message (after message was buffered in the
> network layers, repackaged, read, decoded and formatted), which might be
> quite different from the time it was received.
> 
> You may also want to bear in mind that if a message travels through
> multipler servers, their system time will not be synchronized.
> 
> In my humble opinion, the two must important numbers are:
> - What is perceived by the end user. Which has quite poor granularity
>   (Wow, Ok, Fire the IT guy).
> - What gets published in your company PRs. Which is a surprisingly low
>   number that only happened once in completely unrealistic conditions.


Can't agree more with Jean here! Latency is indeed only as low as it is 
perceived by the end user. Having worked on numerous latency issues, its up to 
the sell side to NOT rely just on what they see (app logs/network logs etc...)A 
good start would be to 

1) Get some kind of feedback (i-e logs) from the end users
2) Set realistic expectations 

Diff buy sides measure latency in their own way and hence have to be looked at 
differently. 


[You can unsubscribe from this discussion group by sending a message to 
mailto:[email protected]]

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Financial Information eXchange" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/FIX-Protocol?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to