How quickly does PropExecutor detect a breach?
Quick answer
On the price tick that causes it. Each account is judged against every new price as it arrives, and a breach is written before the next tick for that account is processed. There is no delay, batch or schedule between a limit being crossed and the account being marked as breached.
Detailed answer
Speed matters because every second between crossing a limit and detecting it is time the account can keep trading.
How tick-by-tick judging works
- A new price arrives from the feed.
- The accounts holding that instrument are re-valued.
- Each account's equity is compared with its loss limits.
- Any breach is written immediately, with its rule, reason and equity.
Why not check every few seconds
- Missed breaches: a spike can cross a limit and recover between checks.
- Late breaches: a trader keeps losing after the limit, then disputes the result.
- Inconsistent outcomes: two accounts with the same equity path could be judged differently depending on timing.
Under load
The engine keeps each account's frozen rule version and its running figures in memory, so judging a tick does not require a database read. Only the rolling peak and day-start values are written in a short batch every second; breach decisions themselves are never batched.
What the trader sees
The terminal shows the breach as it happens, and the dashboard had shown the shrinking headroom up to that point.
PropExecutor team · Updated
Related questions
All 30 questions in The PropExecutor rule engine · Every category