|
|
|
|
|
by msellout
3834 days ago
|
|
A delay of 350 microseconds may very well make the market less turbulent and reduce the prevalence of "flash" crashes. Though the method of implementing the delay might not succeed, a forced delay would alleviate the arms race to lower latency algorithms. Lower latency means fewer computations and less memory, which means the strategy space is smaller. With enough players crowded into a small strategy space, the market becomes more frothy as periodically too many players collide on the same strategy. Placing a lower limit on latency allows a better balance between algorithmic complexity and latency. The strategy space will be larger and hopefully will be large enough that there's room for most everyone to try different strategies, making the market calmer. To get a sense for the mechanism of this phenomenon, check out the El Farol Bar Problem (https://en.wikipedia.org/wiki/El_Farol_Bar_problem). Unfortunately, IEX's proposed implementation of a delay is probably not as good as simply changing the precision of the exchange's clocks. If the exchange decided it would measure time only to the nearest second and orders occurring at the same second would be processed in random order, I expect that would be a better solution. Adding some randomness to the processing order at the 100s of milliseconds scale would go a long way to reducing front-running and overly simplistic momentum strategies. The latter are the main cause of market turbulence. |
|
Or in terms of project planning, if you have 2 day sprints, you can course correct every 2 days and rapidly approach a usable product. If you have 3 month sprints, you might spend 2.9 months building something totally wrong. 2.9 months of moving the wrong way will get you a LOT further off course than a badly planned 2 day sprint.