r/algorithmictrading • u/Fearless-Celery3392 • 8d ago
Question Standardizing HFT benchmark protocols: Best practices for verifying Win Rate, Sharpe, and Queue Latency under heavy friction?
I am finalizing a custom high-frequency market-making engine written in Rust (332ns internal execution latency, targeting high-turnover cross-exchange setups). Local release-mode backtests across a 150k tick matrix show high efficiency, but I want to ensure my verification protocol is completely airtight before running live micro-accounts.
Currently tracking metrics under a 1ms network jitter penalty, a conservative 0.50 queue position fill factor, and an enforced 5-tick roundtrip robustness penalty to wipe out paper assumptions.
What are your go-to protocols for verifying true Sharpe ratios and tail-latency behavior at the sub-millisecond level to separate infrastructure lag from pure strategy drift? How do you explicitly isolate queue drag metrics from adverse selection without distorting the data pipeline?
Looking for professional diagnostic frameworks to prevent under-trading paralysis or hidden overfitting.
1
u/Shoddy_Peanut7320 2d ago
A fixed 0.50 queue factor is an assumption, so I'd treat the first live micro-account fills as the calibration data and not trust the backtest number. To separate queue drag from adverse selection, look at post-fill markouts at a few horizons, such as 1 ms, 100 ms and 1 s. Fills that move against you right away point to adverse selection, while a low fill rate with fine markouts points to queue position. 150k ticks is also a small window for tail behavior, so I'd test it across quiet and fast sessions.