Sub-second execution

Sub-second execution means the full path from a signal arriving to the order being accepted by the venue completes in under one second; it is a property of a specific route and venue, not of a platform in general, and it should be quoted only with a measurement behind it.

Why it matters

The term is used loosely in marketing, so it needs a definition. Intake alone, reading and parsing a message, is easily sub-second and usually under 100 ms on any competent platform. The venue round-trip is what decides the total: a MetaTrader 5 order to a broker can complete in well under a second, while a crypto futures order that also sets leverage and creates a stop and a take-profit involves several calls and typically takes a few seconds end to end. What matters to your results is not the label but whether the measured number is honest and stable, and whether the protective orders are included in it.

How AlgoVesta handles it

AlgoVesta publishes measured figures and avoids the sub-second label where it does not hold. Intake and parsing were measured at 17-67 ms. The complete forex path on MetaTrader 5, from signal to confirmed order, averages about 1.2 seconds, and real forex executions on the demo page are shown in a 0.6 to 1.2 second band. The complete crypto path, including leverage, entry, stop and take-profit with venue-side verification, averages about 4.1 seconds. Those are the numbers shown on the site, and the claims are checked against the measurements before pages are published. Execution runs from dedicated servers near the venues, and the number of calls per order is fixed, so the figures do not degrade as more signals are processed. See the results page and the execution latency entry.

Example

A Telegram signal for XAUUSD is received at 09:30:00.000. Parsing completes at 09:30:00.040, the risk checks pass, and the order is sent to the MetaTrader 5 terminal on the farm; the broker confirms the fill at 09:30:00.9. The same signal for a crypto pair would have its entry confirmed within a similar time but its stop and target confirmed on the exchange about 4.1 seconds after receipt on average.

Common mistakes

• Reading a tens-of-ms figure as end-to-end execution when it measures only intake.
• Comparing a broker's forex round-trip with a crypto exchange's multi-call order path as if they were the same thing.
• Optimising for the entry's speed while the stop-loss is placed seconds later or not at all.
• Trusting a speed claim that is not accompanied by how and when it was measured.