Electronic trading runs on infrastructure that is carefully tuned and then changes continuously. The estate that was measured in January is not the estate running in June.

JANBaseline established. Estate measured.
FEBKernel update
MARNIC firmware revision
APRWorkload migration
MAYHardware replacement
JUNConfiguration change

By June: nothing has failed, and nothing is quite as it was tuned.

Firms watch these systems closely. Whether the estate still conforms to the state it was engineered for is a different question, and answering it today takes investigation: specialist time, applied after behaviour has already moved.

In electronic trading, latency differences are priced. An estate that has drifted from its intended state gives up execution quality silently: nothing fails, nothing pages, it simply performs below the level it was engineered to hold. Research in the Quarterly Journal of Economics values small latency differences in global equities in the billions of dollars a year. Drift concedes that value continuously, usually without anyone having decided to accept it.

AQUILINA · BUDISH · O’NEILL — QUARTERLY JOURNAL OF ECONOMICS, 2022

Performance should be managed continuously, not investigated after it degrades.

LPaC

LPaC is the control layer for latency posture. It expresses the intended performance state of latency-sensitive infrastructure and evaluates the running environment against it, continuously. When the live system departs from its posture, the departure is visible early, with a record of what moved and when, against a stated expectation.

That record changes what an engineering organisation can do. Divergence is acted on from evidence rather than reconstructed from investigation, and what the infrastructure was doing is demonstrable after the fact.

LPaC is built for the engineering leadership of the firms where latency is the business: hedge funds, proprietary trading firms and market makers.

Take control of what’s changing beneath you.

Request a demo