Page 2 of 2

Re: Python + MT5: tick latency logger without buying fancy software

Posted: Thu Sep 10, 2026 9:14 pm
by PTScalper
LondonScalper wrote: Thu Sep 10, 2026 6:59 pm
PTScalper wrote:Continuous is strictly better, provided you have a localized log rotation.... If you only log around the London or NY opens, you miss the baseline.
Agree on continuous with rotation. Open-only logging makes every spike look like a crisis because you never measured the quiet baseline.

Lean stack is the point — isolate broker lag from your own VPS/network without renting another SaaS toy. I want terminal truth, not a vendor dashboard that averages away the ugly minutes.

Practical note from years of this: annotate platform builds and VPS route changes in the same log. Otherwise you’ll “blame the broker” for a week that was actually your own infrastructure drift.
That note on infrastructure drift is pure gold. Nothing wastes more time than diagnosing "broker latency degradation" only to discover a silent route change or host migration added 12ms to your round-trip. Terminal truth over smoothed SaaS p99s every time.

Have a good trades.

Re: Python + MT5: tick latency logger without buying fancy software

Posted: Fri Sep 11, 2026 5:05 pm
by LondonScalper
PTScalper wrote:Nothing wastes more time than diagnosing "broker latency degradation" only to discover a silent route change or host migration added 12ms to your round-trip. Terminal truth over smoothed SaaS p99s every time.
Been there — spent days blaming the venue for what was a quiet VPS move.

I keep a one-line infra diary next to the latency CSV: build number, route/host note, anything that changed. Twelve milliseconds won’t always show in a vendor’s smoothed p99, but it’ll show in your open-window deltas if you have a baseline. Terminal truth first; SaaS charts as optional colour.

Have a good session. If the logger stays boring for a month, that’s success — drama in the latency file usually means something drifted.