Key Implementation Details
Immediate Instantiation: You do not need to call the custom indicator using Indicators.GetIndicator(). Instantiating the built-in AverageTrueRange and passing its Result directly into SimpleMovingAverage inside Initialize() is significantly faster and uses less memory.
Log Throttling: When a strategy triggers a persistent "Buy" signal (e.g., price stays within an entry zone for 30 seconds), OnTick() will attempt to execute thousands of times. The LogRejection() method restricts the journal output to once per minute, ensuring your broker logs remain readable.
State Reset: _lastRejectionLogTime is reset to DateTime.MinValue upon successful execution, ensuring the next rejection is logged immediately, even if it happens on the very next candle.
Brokers with good VPS partnerships for low latency
Re: Brokers with good VPS partnerships for low latency
Preserve your own money. Scale with the market's money. Exponential growth is the ultimate key.
-
LondonScalper
- Posts: 965
- Joined: Sat Sep 05, 2026 7:54 am
Re: Brokers with good VPS partnerships for low latency
I'd treat any list of broker and VPS pairings as a starting point to test rather than a recommendation, because server locations change with platform and entity. IC Markets is a good example: MT4/MT5 accounts are served from New York and cTrader from London, so an LD4 VPS is right for one account type and adds a transatlantic leg for the other.
The resource point is the one I'd keep. My own flatten drill failed once on a cheap plan, not because of the network, but because the remote session froze while the terminal was loading a second chart set. Since then I test with everything open that I'd run on a normal morning, not an empty desktop.
The Pine zones are fine as a reminder, but in London most of my slippage comes from the minutes after 08:00 and around data. I'd rather mark those by the clock than by a volatility spike detected after the fact.
The resource point is the one I'd keep. My own flatten drill failed once on a cheap plan, not because of the network, but because the remote session froze while the terminal was loading a second chart set. Since then I test with everything open that I'd run on a normal morning, not an empty desktop.
The Pine zones are fine as a reminder, but in London most of my slippage comes from the minutes after 08:00 and around data. I'd rather mark those by the clock than by a volatility spike detected after the fact.
-
LondonNewsTrader
- Posts: 421
- Joined: Mon Sep 21, 2026 9:30 am
Re: Brokers with good VPS partnerships for low latency
There's a mismatch between the parameters and the attribute. The inputs are labelled "Server HH:mm", but the indicator is declared with TimeZone = TimeZones.UTC, so Bars.OpenTimes are in UTC and the 10:00 to 18:30 window is applied in UTC. That's 11:00 to 19:30 London in summer and 10:00 to 18:30 in winter, rather than whatever the server-time intention was. Either relabel the inputs as UTC or change the attribute.
The spike test is also less sensitive to news than it looks. A single release bar ten times the normal range only lifts a 14-period simple ATR to about 1.64 times its previous value, since the new bar is averaged with 13 normal ones. Compared with a 50-bar average of the ATR, that won't reach 2.5x, so isolated release spikes are mostly missed. The flag fires on sustained high volatility, which is useful, but a separate check of the current bar's range against the ATR would catch the single-candle events.
-
FXS Prop Desk
- Posts: 1689
- Joined: Wed Oct 07, 2026 9:52 am
Re: Brokers with good VPS partnerships for low latency
Running a flatten drill is the right priority. Readers should verify current VPS partnerships directly with brokers, since these change over time and some offers depend on minimum deposits or monthly volume. Checking the broker's server location in the platform and measuring latency from a trial VPS is the most reliable way to confirm a pairing actually delivers.
A good practical test is to run a trial VPS for a week, log the latency to the trade server at different times, and run the flatten drill during the London open.
A good practical test is to run a trial VPS for a week, log the latency to the trade server at different times, and run the flatten drill during the London open.
FXS Official Team | The Idea Lab & Strategy