Setup and operations
VPS Ping vs Order Execution Time | New Hope PRO

New Hope PRO · Execution workshop
Your VPS shows 5 ms, but a trading order takes 200 ms to complete. Those numbers can both be correct. The useful question is which part of the journey each one measures. Here is a practical way to read the sequence, compare timings and investigate a slow trade in New Hope PRO.
Three clocks that should not be confused
Think of ordering a delivery. Reaching the restaurant quickly does not tell you when your meal will arrive. Trading has its own sequence: a quote reaches the software, the strategy decides what to do, a request leaves the computer, and a response returns.
Network ping checks a connection. Windows ping measures the round trip of an ICMP test message, not the lifecycle of an order. A platform's connection indicator may use a different method, so check what that particular number represents. Microsoft's ping reference describes the Windows measurement.
Quote-delivery delay concerns market data. Order-execution time concerns a trading request and the chosen finishing event. An acknowledgement and a fill are different events. MetaQuotes explicitly explains that a successful OrderSend response does not, by itself, prove execution. See the OrderSend documentation.
A 200 ms order, step by step
The following is an educational example, not a New Hope performance test or a broker measurement. All four timestamps are recorded on the same computer using the same clock.
Event | Local time | Since signal |
|---|---|---|
Signal recorded | 12:00:00.000 | 0 ms |
Request sent | 12:00:00.004 | 4 ms |
Acknowledgement received | 12:00:00.018 | 18 ms |
Fill confirmation received | 12:00:00.204 | 204 ms |

Illustrative timing report. The intervals describe what the client observed; they do not reveal every internal broker step.
Signal-to-send is 4 ms. Send-to-acknowledgement is 14 ms. Send-to-fill-confirmation is 204 − 4 = 200 ms. The whole observed signal-to-confirmation interval is 204 ms. A separate 5 ms ping is not added to these intervals because network travel is already part of the measured request journey.
Do not subtract a broker timestamp from your computer's timestamp unless their clock alignment is known. A clock offset can look like an execution delay. For partial fills, record both the first fill and completion of the requested quantity.
Read the New Hope PRO log as a sequence
The New Hope PRO 1.8.11 update brings colour-coded logs covering signals, prices, slippage, profit, closing reasons and execution times. Start with one order and connect its related entries. Read the timing alongside the direction, requested quantity, price and final outcome.
The default 200 ms boundary is a log-classification threshold. It does not promise a 200 ms fill or declare every faster trade good. A quick fill at an unfavourable price still needs investigation; a slower entry can have a different price outcome.
The update also prepares trading libraries without sending orders. That addresses initial preparation before the first request. Keep first-order observations separate when comparing them with a session that has already been running.
One fast trade does not describe a trading session
Here is a deliberately small, synthetic dataset of 20 send-to-fill-confirmation times, in milliseconds:
84, 88, 90, 92, 95, 98, 100, 104, 108, 112, 124, 128, 132, 138, 145, 152, 164, 180, 260, 520.
Measure | Result | What it adds |
|---|---|---|
Median | 118 ms | The middle of this sample |
Mean | 145.7 ms | The average, influenced by the slowest order |
95th percentile, nearest-rank method | 260 ms | The 19th observation after sorting |
Maximum | 520 ms | The slowest observed order |
Above 200 ms | 2 of 20, or 10% | How often this example exceeds the chosen boundary |
A headline saying “118 ms execution” would hide the 520 ms observation. Keep both the typical case and the slow tail. Twenty examples explain the calculation; they are too few to establish stable behaviour across sessions. Also count rejected requests and timeouts separately, otherwise a report of successful fills can overlook the most troublesome requests.

Educational data, not New Hope performance. The 95th percentile uses the nearest-rank method.
Find the part you can actually improve
The connection becomes unstable. Compare disconnect times with the VPS network and resource records. Identify the actual account server, not just the broker's brand or office location.
The pause appears before sending. Check whether it coincides with startup, high CPU use, disk activity or several programs starting together.
Acknowledgements arrive, but fill confirmations are late. Keep the order IDs and timestamps. They give support something specific to investigate. The client log alone cannot assign the delay to one internal broker component.
Timing looks acceptable, but prices are poor. Review the spread, order size and direction-adjusted slippage. Speed and price quality belong in the same report.
cTrader's documentation likewise distinguishes fast platform processing from the eventual fill, which can depend on the execution chain. Its trading-conditions guide provides the platform's explanation.
Compare changes fairly
Before moving a VPS, save a baseline: account server, connection type, instrument, quantity, software version, session, time zone and measurement definition. Change one factor where practical. Compare similar trading periods and report differences in spread, rejected requests and slippage as well as time. Do not open extra live trades solely to build a timing sample.

New Hope PRO interface supplied for the 1.8.11 release. Use the displayed time zone when comparing an event with your log.
The calendar provides context for a timing review. Mark whether an observation was near a scheduled event, then examine the actual spread and executions in that period. A nearby announcement is a reason to inspect the data, not proof that it caused the delay. The screenshot shows calendar information; it does not demonstrate an automatic strategy filter.
A lower connection ping can help one part of the journey. It cannot guarantee a faster complete trade. Our VPS compatibility guide explains the hosting choice, while the execution audit checklist expands the trade-level review. If the question is which quote arrives first, use the separate feed-comparison workflow.
Understand the workflow before changing a live setup
Explore New Hope PRO, then use the free lessons and interactive practice in New Hope AREA to learn the setup sequence. Educational access does not require a software purchase.
More articles




