You don't need to adjust anything. My phrase was for a general case "in your internet and your ping can be anything and in reality depending on your network you will get a transaction in 0-N ms". And it's more likely to be 0 ms than more.
Here is the verification code with control of all transactions in asynchronous mode:
It shows all stages of transactions with the cumulative total of time spent from the start. By transaction types you can see what was added to the terminal and when.
The total time is 11.45 ms.
Thank you very much for the clear code! According to your results, there is really nothing to correct. I made a mistake.
Keep hotkeys ready for instant screen recording. Or record everything around the clock. You can always cut out a problematic piece and present it as a proof. For now, just words.
That's an extract from the Temninal's log, not my own log!
Yes, that's right. Sorry, I confused it with a mate who was counting timings incorrectly.
Here's what happened at the time: it's a question for the exchange - why does it always behave like that on minimal movements and considers it normal to execute orders in such a time.
You wanted to place a limit order at 47.56 close to the market and it is likely that the exchange slowed down accepting orders for a close price interval on purpose, so that there would be no surprises for it:
From the performance point of view there can be no questions, as the volume there was ridiculous, 320 lots per minute.
I have shown my performance in a calm market above.
fxsaber: Keep hotkeys at the ready for instant screen recording. Or record everything around the clock. You can always cut out the problematic part and present it as evidence. For now, just words.
Can you please highlight the lines in your example-log where the exchange's brakes will be visible when it behaves like this?
2016.09.1418:32:53.234 Test (BR-12.16,H1) TRADE_TRANSACTION_HISTORY_ADD BR-12.16: 0.00 time: 11.455 ms
2016.09.1418:32:53.232 Test (BR-12.16,H1) TRADE_TRANSACTION_DEAL_ADD BR-12.16: 47.130 time: 8.778 ms
2016.09.1418:32:53.231 Test (BR-12.16,H1) TRADE_TRANSACTION_ORDER_DELETE BR-12.16: 0.00 time: 8.457000000000001 ms
2016.09.1418:32:53.231 Test (BR-12.16,H1) TRADE_TRANSACTION_ORDER_UPDATE BR-12.16: 0.00 time: 8.202999999999999 ms
2016.09.1418:32:53.231 Test (BR-12.16,H1) TRADE_TRANSACTION_REQUEST : 0.044326441 time: 8.151 ms
2016.09.1418:32:53.228 Test (BR-12.16,H1) TRADE_TRANSACTION_ORDER_UPDATE BR-12.16: 0.00 time: 5.196 ms
2016.09.1418:32:53.228 Test (BR-12.16,H1) TRADE_TRANSACTION_REQUEST : 0.044326441 time: 5.171 ms
2016.09.1418:32:53.227 Test (BR-12.16,H1) TRADE_TRANSACTION_ORDER_ADD BR-12.16: 0.00 time: 4.184 ms
2016.09.1418:32:53.223 Test (BR-12.16,H1) Start...
2016.09.1418:32:49.753 Test (BR-12.16,H1) AsyncTradesTest: last ping 2.15 ms, build 1417
It will most likely become noticeable from here, but will definitely be visible on the last two transactions:
2016.09.1418:32:53.234 Test (BR-12.16,H1) TRADE_TRANSACTION_HISTORY_ADD BR-12.16: 0.00 time: 11.455 ms
2016.09.1418:32:53.232 Test (BR-12.16,H1) TRADE_TRANSACTION_DEAL_ADD BR-12.16: 47.130 time: 8.778 ms
2016.09.1418:32:53.231 Test (BR-12.16,H1) TRADE_TRANSACTION_ORDER_DELETE BR-12.16: 0.00 time: 8.457000000000001 ms
2016.09.1418:32:53.231 Test (BR-12.16,H1) TRADE_TRANSACTION_ORDER_UPDATE BR-12.16: 0.00 time: 8.202999999999999 ms2016.09.1418:32:53.231 Test (BR-12.16,H1) TRADE_TRANSACTION_REQUEST : 0.044326441 time: 8.151 ms
2016.09.1418:32:53.228 Test (BR-12.16,H1) TRADE_TRANSACTION_ORDER_UPDATE BR-12.16: 0.00 time: 5.196 ms
2016.09.1418:32:53.228 Test (BR-12.16,H1) TRADE_TRANSACTION_REQUEST : 0.044326441 time: 5.171 ms
2016.09.1418:32:53.227 Test (BR-12.16,H1) TRADE_TRANSACTION_ORDER_ADD BR-12.16: 0.00 time: 4.184 ms
2016.09.1418:32:53.223 Test (BR-12.16,H1) Start...
2016.09.1418:32:49.753 Test (BR-12.16,H1) AsyncTradesTest: last ping 2.15 ms, build 1417
It will most likely become noticeable from here, but will definitely be visible on the last two transactions:
Thanks. The help and the article are rather sparse on the internal processes behind each type of trade transaction.
In your clarification it appears that the first four lines (8ms) are not an exchange yet. Where is it possible to read what actually happens? Because there is no understanding and it is not clear where to get it.
Thanks. The help and the article are rather sparse on the internal processes behind each type of trade transaction.
In your clarification it turns out that the first four lines (8ms) are not an exchange yet. Where is it possible to read what actually happens? Because there is no understanding and it is not clear where to emphasise it.
No, I didn't say that.
I sketched the code hastily and did not describe all the fields. Check yourself in the debugger each input to the function of my script and print out more fields, please.
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
There was strong movement on Brent today
And at this moment MT5 took care of these delays.
You don't need to adjust anything. My phrase was for a general case "in your internet and your ping can be anything and in reality depending on your network you will get a transaction in 0-N ms". And it's more likely to be 0 ms than more.
Here is the verification code with control of all transactions in asynchronous mode:
Here is its output on a real account just now:
You should read it from bottom to top.
It shows all stages of transactions with the cumulative total of time spent from the start. By transaction types you can see what was added to the terminal and when.
The total time is 11.45 ms.
Today there was a strong movement on Brent.
And at this moment MT5 took care of these delays.
What are you talking about, Renate?
That's an extract from the Temninal's log, not my own log!
Yes, that's right. Sorry, I confused it with a mate who was counting timings incorrectly.
Here's what happened at the time: it's a question for the exchange - why does it always behave like that on minimal movements and considers it normal to execute orders in such a time.
You wanted to place a limit order at 47.56 close to the market and it is likely that the exchange slowed down accepting orders for a close price interval on purpose, so that there would be no surprises for it:
From the performance point of view there can be no questions, as the volume there was ridiculous, 320 lots per minute.
I have shown my performance in a calm market above.
Keep hotkeys at the ready for instant screen recording. Or record everything around the clock. You can always cut out the problematic part and present it as evidence. For now, just words.
Today there was a strong movement on Brent.
And at this moment MT5 took care of these delays.
Only MT5 has nothing to do with these delays.
It was the exchange that responded for so long.
Only MT5 has nothing to do with these delays.
It was the exchange that took so long to respond.
Can you please highlight the lines in your example-log where the exchange's brakes will be visible when it behaves like this?
It will most likely become noticeable from here, but will definitely be visible on the last two transactions:
It will most likely become noticeable from here, but will definitely be visible on the last two transactions:
Thanks. The help and the article are rather sparse on the internal processes behind each type of trade transaction.
In your clarification it appears that the first four lines (8ms) are not an exchange yet. Where is it possible to read what actually happens? Because there is no understanding and it is not clear where to get it.
Thanks. The help and the article are rather sparse on the internal processes behind each type of trade transaction.
In your clarification it turns out that the first four lines (8ms) are not an exchange yet. Where is it possible to read what actually happens? Because there is no understanding and it is not clear where to emphasise it.
No, I didn't say that.
I sketched the code hastily and did not describe all the fields. Check yourself in the debugger each input to the function of my script and print out more fields, please.
Thanks. The help and the article are rather poorly written about the internal processes behind each type of trading transaction.
An example of a possible listener of trading events is given in the article Where to start when creating a trading robot for the Moscow Exchange MOEX