What the practice server shows and what only a live one adds — Namibia

Measured order execution — Standard

How orders actually filled when real market orders were placed on Exness’s MT5 feed — fill time, slippage and rejects by order size:

Small sample (a few round-trips per size); indicative. The same pricing engine feeds every platform the broker offers.

MetaTrader 5 (MT5) at Exness

• A practice server and a live server are two separate destinations for the same installed program.
• The instrument list a window shows is the list published by the server it is connected to, so two connections on one machine can hold different sets of names.
• How far back a chart can be filled in is a property of the connection rather than of the program.
• The order screen, the pending-order fields and the analytical tools behave identically on either connection — the difference begins after an order leaves the window.
• Anything concerning the account record rather than the chart sits outside the terminal entirely and is not reachable from either server.
• Both connections can be held in the same program at once and switched between from the account list inside it.
• A window gives away which side it is on: the account entry it is connected through names its own kind.

What is identical on both sides

Everything that is part of the program travels with the program. The layout, the chart windows, the fields on the order screen and the analytical tools are properties of the installation, so they are present the first time it opens and they do not improve when a live account is attached to it.

That is the useful half of the arrangement. It means the whole of the interface can be learned at the practice level, and nothing learned there has to be relearned later, because it was never the account that was teaching it.

What belongs to the server rather than the program

The list of instruments is published by the server, which is why the same installation can show one set of names on one connection and another set on the next. The same applies to how much history a chart can be filled with: the program asks, and the server answers with what it holds.

This is the part that a screenshot cannot settle. Two identical-looking windows can be sitting on different lists, and the only reliable way to know which is which is to look at the account entry the window is connected through rather than at the chart in front of it.

Where looking ends and working begins

An order placed on a practice connection is answered by the practice server, and the answer is complete in its own terms: the window updates, the position appears, the numbers move. What it is not is an obligation. The result exists only where that account exists.

The boundary is therefore not a feature that is switched on. It is a change of counterparty. Everything that is a matter of seeing — the interface, the tools, the shape of the data — is available at the practice level; everything that is a matter of consequence belongs to the connection that has a real account behind it.

Telling which server a window is on

1. Open the account list inside the program: each entry states the kind of account it is, and the connected one is the one in use.
2. Compare the instrument names in the window against the ones the other connection shows; different lists mean different servers.
3. Check how far back a chart will scroll — depth is a property of the connection, not of the installation.
4. When both connections are held in the same program, switch by selecting the other entry rather than by reinstalling anything.

Nothing has to be fetched again to move between the two; both are connections made by the same installed program.

Which side each thing belongs to

Anything acting on the account record itself is outside the terminal and is reached from neither connection.

Related Exness pages