FORTS long delays in order execution - page 9

 
papaklass:

Is the broker involved in sending orders to the exchange?

If so, ask for a report on those same orders.

PS: Is there time delta between terminal time and exchange time? If yes, what is it?

Is it not obvious:

1 order "left" the terminal2014.11.20 10:07:06.048

came to the exchange -10:07:07.299

Although the time difference is more than 288 ms, this only indicates that the

MT-5 server is not synchronized with exchange time (I wrote a complaint about time synchronization).

Exchange order processing time < 1 ms (in the logs at all 9 MICROSECONDS )

etc ....

 
papaklass:

Not obvious.

If the order left the terminal 06.048, then how do you know the execution time 288 ms. You have a telepathic terminal, knows the execution time in advance

I apologise, it's the time the terminal received the response.

Apparently it's my computer's time. BUT the question was "WHO'S THINKING?"

The MT-5 server or the Exchange, the answer is obvious to me.

 

There are different order times:

  1. Creation time on the terminal.
  2. Transmission time to the MT5 server.
  3. Time of acceptance by the MT5 server.
  4. Transmission time to an exchange.
  5. Exchange acceptance time.
  6. Processing time by exchange.
  7. Handling time by MT5 server.
  8. Acceptance time by MT5 server.
  9. Time to be sent by the MT5 server to the terminal.
  10. Time of receiving by the terminal.

Let us denote by [N-M] - the difference between times of N and M in our list of times.

According to the logs exchange says that [7-5] < 1ms. If we have appropriate logs, it's easy to understand why [10-1] > 300 ms.

Obviously, developers are not fools and already found a strange place. Finding the cause and fixing it is an important and maybe not easy task.

 
papaklass:
See how that works out.... and you've already been sassed.
You, papaklass, see rudeness everywhere....
 
zaskok:

There are different order times:

  1. Creation time on the terminal.
  2. Transmission time to the MT5 server.
  3. Time of acceptance by the MT5 server.
  4. Transmission time to an exchange.
  5. Exchange acceptance time.
  6. Processing time by exchange.
  7. Handling time by MT5 server.
  8. Acceptance time by MT5 server.
  9. Time to be sent by the MT5 server to the terminal.
  10. Time of receiving by the terminal.

Let us denote by [N-M] - the difference between times of N and M in our list of times.

According to the logs exchange says that [7-5] < 1ms. If we have appropriate logs, it's easy to understand why [10-1] > 300 ms.

Obviously, developers are not fools and already found a strange place. Finding the cause there and fixing it is an important and maybe not easy task.

There is no objection, but it is clearly written that the execution time of the order (for the first application) - 288 ms

The exchange log shows that this order was processed < 1 ms.

Let's take another way, namely:

There is a chain: terminal - internet - broker's server - Plaza - exchange - Plaza - broker's server - internet - terminal.

I will now call the broker and get my connection tested......

Документация по MQL5: Стандартные константы, перечисления и структуры / Торговые константы / Свойства ордеров
Документация по MQL5: Стандартные константы, перечисления и структуры / Торговые константы / Свойства ордеров
  • www.mql5.com
Стандартные константы, перечисления и структуры / Торговые константы / Свойства ордеров - справочник по языку алгоритмического/автоматического трейдинга для MetaTrader 5
 

The broker sent the following:

mkdir c:\net_test

cdir c:\net_test\

ping -l 1024 -n 100 193.219.127.84> c:\net_test\serverMT5_ping.txt

tracert 193.219.127.84> c:\net_test\serverMT5_tracert.txt

I'll post the results in five minutes...

 
papaklass:
Well, finally, let's get down to the subject matter. :)
No need to be snide...
 

Pinging 193.219.127.84 with 1024 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 193.219.127.84:

Packets: Sent = 100, Received = 0, Lost = 100 (100% loss),


Tracing route to 193.219.127.84 over a maximum of 30 hops


1 <1 ms <1 ms <1 ms 192.168.1.1

2 * * * Request timed out.

3 * 2 ms 2 ms mtk-105-lag-91.msk.ip.ncnet.ru [77.37.254.198]

4 3 3 ms 2 ms 3 ms m10-cr01-be4-91.msk.ip.ncnet.ru [77.37.254.197]

5 3 ms 2 ms 3 ms macomnet-eth1000-m9-ix.macomnet.net [193.232.244.59]

6 3 ms 3 ms 4 ms FastEthernet0-0.ncc-8.MAcomnet.NET [195.128.64.67]

7 4 ms 4 ms 4 ms FKO-09-DCH-0910-MAcom.Macomnet.NET [212.5.127.81]

8 5 ms 4 ms 5 ms 193.219.127.225

9 5 ms 4 ms 4 ms 193.219.127.225

10 5 ms 6 ms 5 ms 193.219.127.225

11 5 ms 5 ms 6 ms 193.219.127.225

12 6 ms 5 ms * 193.219.127.225

13 7 ms * * 193.219.127.225

14 7 ms * * 193.219.127.225

15 8 ms * * 193.219.127.225

16 6 ms * 193.219.127.84 reports: Destination net unreachable.


Trace complete.

 

Everything is closed.

Requested the broker's logs for my account (my order arrival time)

They promised to send it, we are waiting ....

In the meantime, let's remove the exchanger from the chain:

terminal - internet - broker's server - Plaza - exchange (< 1ms) - Plaza - broker's server - internet - terminal

Maybe someone will tell me what it is:

9 5 ms 4 ms 4 ms 193.219.127.225

10 5 ms 6 ms 5 ms 193.219.127.225

11 5 ms 5 ms 6 ms 193.219.127.225

12 6 ms 5 ms * 193.219.127.225

13 7 ms * * 193.219.127.225

14 7 ms * * 193.219.127.225

15 8 ms * * 193.219.127.225

 
papaklass:

Where are the order processing timings?

Or are you saying that your communication with your broker is bad?

Requested the broker's logs for my account (my order arrival times)

Just to check the communication 100%.