Not-So-Hidden Latency Part 2 - Trader/Comprehension Latency
Following on from my previous post on Not-So-Hidden Latency, another topic Tom Groenfeldt and I had started discussing earlier this week was something we at the lab have been thinking about for some time: trader latency or comprehension latency. I’ll explain below.
As the search for low latency has continued, it has focused on two things: (a) reducing the latency in receiving and processing market data and (b) reducing the latency in executing a transaction. Now, insofar as algorithmic trading is concerned, the search has also focused on reducing the time it takes for algorithms to make execution decisions based upon that incoming market data, i.e., the time it takes them to get from (a) to (b).
But what about the scenario where the task of making that execution decision lies not with an automated system, but rather with a human trader? At that point, you have to start considering the latency from when the data first reaches the trader’s eyes to when the trader finally enters the keystrokes to execute a trade. That is what we call ‘trader latency’ or ‘comprehension latency’, i.e., the time between when a trader sees information and then is able act on that information.
The challenge is to reduce that time period while, at the same time, allowing traders to deal with ever greater volumes of data updating at ever greater frequencies. This not-so-hidden latency has, to date, been sorely overlooked. The solution is to come up with innovative ways to display that information to users. That thesis is the very basis behind our Advanced Data Visualization practice (see the paragraph titled “Monitor More Volume with Richer Context” on our Services page). The market liquidity visualizations, the fixed income pricing visualizations, and all of the winners from our WPF in Finance challenge are excellent examples of means to that end.
In all the years that the industry has been developing trading systems, user experience has rarely been a significant concern. Thankfully, the industry is finally realizing that reducing latency won’t help if the only result is that the cells on a trader’s workstation blink faster. You actually have to come up with innovative ways to allow traders to quickly and intuitively deal with that data.
From where we stand now, we certainly see that changing as more and more banks bring on companies like Lab49 to help them focus on things like user experience. To the extent that that is happening, we’re obviously all for it.


March 21st, 2008 at 10:26 am
I would argue that trading actions that require low latency to be successful are ripe for automation. I think that there is a commiditization cycle that moves trading strategies from high return, high touch, to low return, high volume, with automation as the enabling agent. If the response time of the trader is a competitive advantage, then I would think there is huge payback in automating that response, since the automated response will be orders of magnitude quicker.
March 24th, 2008 at 1:46 pm
I’m not contesting what you’re saying. There’s a spectrum of opportunities from high return/high touch/low volume to low return/low touch/high volume. Visualization technologies are a catalyst that helps push things down that spectrum insofar as they help traders to intuit possible analyses of market data. Yes, those intuitions, once verified and proven, should absolutely be automated.