Bullets Dodged, Bullets Caught
Suppose you have a resting order in the limit order book. Your fair value model suggests that you should pull the order. But the decision of whether or not to send a cancel request is a bit more subtle.
There are two possibilities: (a) your model is correct and (b) your model is wrong.
The difference is that in the latter case, you cancel will always succeed (and you will have given up queue priority unnecessarily). In the former case, however, when a cancel is indeed justified, there is a fair chance that your cancel will arrive too late at the exchange - that the order has already traded. So you have to evaluate the expectancy of the cancel taking into account the probability that it will have no effect.
Fig. 1 below shows the frequency of timely (blue) and late (grey) cancel requests vs. the gateway-in-timestamp difference w.r.t. the trade which would have or did fill these resting orders. The bottom panel shows the markout PnL (trade price vs. T+10 s mid) associated with each latency bucket. The bars to the left of zero is the markout PnL that the order would have yielded if it had not been canceled. The bars to the right of zero is the actual (but unintended) markout PnL for traded orders whose cancel request came too late.
Observations
High-Frequency Market Making
2 天前It would also be interesting to see this on a scale of +/- 10 us. I suppose it depends on what the signal is, but in my world, 100 us late is very late. Also, which products/exchanges does this cover?
High-Frequency Market Making
3 天前Stefan Schlamp - is the second panel cumulative or average-per-order?
Capital Markets Execution Consultant for Public Companies | Share Buy-backs | Group Exco | Global Head Execution Services | Algorithmic and Program Trading | Governance | Risk Managment | SM&CR Significant Person
3 天前Stefan Schlamp- If you look out the grey side for longer, say to 1 second are there any noticeable other bumps? I imagine there are still quite a number of systems which have much greater latencies than 1ms - ie the passive SOR still sits on another infrastructure entirely, and often in a different location.