# Tag Info

3

The round-trip latency from point A to a matching engine at point B can be thought of being comprised of two components: $RTT_{total,A \rightarrow B} = RTT_{network\_transit,A \rightarrow B} + MPL_{matching\_engine,B}$ Where $RTT$ is the round-trip time and $MPL$ is the message processing latency (how long it takes to receive a message and produce an event)...

2

It is possible that they are getting "news", but what I feel these firms are doing is connecting to EMSX offered by Bloomberg which is an electronic trading platform. Which is why they would probably invest in sending microwave shots of data back to NJ. The data is : which broker offers which security at what rate. Earlier access to data implies that they ...

2

That will depend on the protocol you are using for market data (UDP, FAST, MDP, ITCH, etc.) and order routing (FIX, OUCH, etc.). For example, the latency to parse a UDP tick and to place a FIX order was around 8 micros as measured by tcpdump, using CoralFIX and CoralReactor. Disclaimer: I'm one of the developers of CoralFIX

1

Exchanges provides the following six timestamps: Gateway In Timestamp-T1. Time at which the order was received by the Gateway from the members TCP connection. Gateway Out Timestamp-T2. This is the time when the order was dispatched by the Gateway to the Matching engine. Matcher In Timestamp-T3. This is the time the order was received by the Matching engine....

Only top voted, non community-wiki answers of a minimum length are eligible