Hot answers tagged

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 ...


2

IEX is an ATS. The ECN/ATS business is dominated by rampant and well known conflicts of interest. A part of the IEX value proposition from the beginning was to offer an alternative to traders who were disenfranchised by this market structure. If maker-taker rebates are part of your trading business model or if you engage in any strategy that could be deemed ...


1

For ultra-low-latency network applications it is mandatory to use a single-threaded, asynchronous, non-blocking network library. You can and should handle multiple TCP connections inside the same reactor thread which will be pinned to a dedicated and isolated cpu core. To give you an idea of TCP latencies you can take a look on our benchmarks using ...


1

You probably want more than a low "TCP latency". Anyway, what latency is it? The TCP layer to connect to your 10Go (i.e. The implementation of the TCP protocol only)? The implementation of a protocol to read the market data (direct native feed? FIX?)? Or to "move" the content of the feed to a zone of memory shared with your application? And what about the ...


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 ...



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