Using ITRS performance management capabilities, our clients are initiating remedial actions as part of an automated support process, allowing them to identify and rectify problems before they become critical.
So how do you add instrumentation to high frequency trading engines without impacting the pre-trade latency target? Here are four examples:
Check that the supporting post-trade checks are actually running on their designated servers.
Check that the Algo engine itself is not consuming unexpectedly high amounts of CPU and memory resource; this could indicate a never ending looping problem.
At various points the post trade risk checks should be making audit entries in log files: ITRS can check that these are actually taking place?
Are the post trade processing applications overloading their designated servers? This might indicate that too many tasks are being generated by erroneous trades fed into the execution venue and that the post-trade checks are building up to such an extent that they are not processed in a timely fashion.
To find out more, contact Patrick McVeigh at pmcveigh@itrsgroup.com