2 ms·
It's basically DoS attacks for other market participants. Basically all algo trading systems need to cancel/modify their limit orders to keep things relative t
by noname123 16y ago
It's basically DoS attacks for other market participants.
Basically all algo trading systems need to cancel/modify their limit orders to keep things relative to the last traded price and the whole quote book. The way they maintain their own quote book is through some data feed's API. e.g.,
Processing messages via onBidChange(double price, int bidSize); suppose you send a million buy orders at $2.00 when the stock price is trading at $6.00; your orders won't get executed, but your competitor who's processing these messages will be busy processing these message. You ignore the bottom of the book because you know your own garbage orders while you focus on processing messages at the top of the book in case of a inter-market/equity-options-futures arbitrage opportunity arises for 200ms. Your competitor was busy processing your garbage orders for 200ms; he/she either can't arb the trade as fast as you can, or they are the mutual fund algo and they can't cancel/modify their VWAP limit orders fast enough, while you trade in and out 2000 shares for $0.01/share profit plus liquidity rebates in that 200ms.
- yummyfajitas 16y agoFor most of the graphs shown in this article, the message bursts are occurring at the top of the book (for that particular route). Those orders have a fairly good chance of being filled if the price moves unfavorably. If you want to suggest they are hacking someone, I'd propose an alternative target: the exchange. Say the current NBBO is on INET, but the pattern is on BATS. Once the price on INET drops below the pattern level on BATS, INET needs to devote effort to communicating with BATS to determine whether to fill orders or route them. That adds latency.