FORTS long delays in order execution - page 7

 
Mikalas:
I have a different IP.
I'm the one who wrote nonsense - it's my IP))
 
Hey, hotshots, do your IPs a wash. Or do you want to get remote attacks by accident?
 
Dima_S:
I'm the one who wrote nonsense - it's my IP))

:)

 
Mikalas:

Renat, with all due respect, it's hard to believe that at 21-00 o'clock the stock exchange registers

order for illiquid instrument (there are few bids in the ticker, therefore there is no queue) for 388 ms.

What does it mean to believe?

You know that there is a whole world of execution behind the walls of MT5, where all the work takes place. MT5 itself works with zero load (even if we gather all the stock traders in Russia, the server won't even notice the load) and all the potential load variation is outside our limits.

Why do you think the pipe (which doesn't even theoretically have variation latency, as there is no subject to braking) is introducing delays and not the exchange itself? And you see in other trades that it is a real pipe with no intelligence that simply broadcasts trades at top speed.


Who works with external liquidity (writes gateways, uses them, even without linking to MT4/MT5), knows that there are always "inexplicable" lags in execution speed. 90% of the time everything flies perfectly at a speed close to a double ping, but sometimes the runtime jumps ten times higher than normal. And not even on the news.

 
Renat:

What does belief have to do with it?

You know that behind the walls of MT5 there is a whole world of execution where all the work goes on. Otkritie's MT5 itself runs with zero load (even if you gather all the stock traders in Russia there, the server wouldn't even notice the load) and all the potential load variation lies outside our borders.

Why do you think that the pipe (which does not even theoretically have variation latency, as there is no subject of braking) is causing delays, and not the exchange itself? And you see in other trades that it is a real pipe with no intelligence that simply broadcasts trades at top speed.


Who works with external liquidity (writes gateways, uses them, even without linking to MT4/MT5), knows that there are always "inexplicable" lags in execution speed. 90% of the time everything flies perfectly at a speed close to a double ping, but sometimes the runtime jumps ten times higher than normal. And not even on the news.

Are you hinting at bugs in the exchange itself that are so easily reproducible? Indirectly, this can be refuted by the absence of such complaints from high-frequency traders via Plaza.

The exchange forums would "eat" the exchange at once for such brakes. It's not the exchange that is slowing it down, that's for sure.

 
zaskok:

Hinting at bugs in the exchange itself that are so easily reproducible? Indirectly, this can be refuted by the absence of such complaints from high-frequency traders via Plaza.

The exchange forums would "eat" the exchange at once for such brakes. It's not the exchange that's slowing it down, for sure.

You cannot assume that you are playing a game with your computer, which is strictly deterministic in its actions and response speed. The method of comparison through "public lack of complaints" is inappropriate in this case. Not only that, but those who write their integrations have had enough of interesting effects, have taken it for granted and no longer discuss it in public. We, on the other hand, don't write our complaints about some gateways in public forums, even though we sometimes encounter absolutely unnecessary things.

In order to get an accurate answer on the timings, you must correctly form a request, ask a specific question on the specified trade to the broker's support service and ask for a log of the execution of the specific trade. For only the broker has accurate execution logs all the way around. It is important to ask the right question so that it is not seen as excessive and generic.

It is irrational to ask these kinds of questions in a forum knowing that the other side does not have these logs.

 
Renat:

You cannot assume that you are playing a game with your computer, which is strictly deterministic in its actions and response rate. The "public no complaints" comparison method is not appropriate in this case.

In order to get an accurate answer on the timings, you need to properly form a request, ask a specific question on the specified trade to the broker's support team and ask for the execution log of the specific trade. For only the broker has accurate execution logs all the way around. It is important to ask the right question so that it is not seen as excessive and generic.

It is irrational to ask these kinds of questions in a forum knowing that the other side does not have these logs.

I will take the liberty, on behalf of all traders who use MT5 Expert Advisors, to ask you to look into these specific cases (logs are presented) and give a substantiated answer here, what are these brakes and who is really behind them? I'm not the only one stressed by this. Take the suspicion away from the platform, confirm the reputation of the highly qualified developers of the "pipe". The answer now very much resembles a typical arrow transfer (forgive me for my Phranusian).
 
zaskok:
I will take the liberty, on behalf of all those trading on the exchange via MT5 EAs, to ask you to look into the specific cases (logs are given) and give a reasoned answer here, what are the brakes and who is really behind them? I'm not the only one stressed by this. Take the suspicion away from the platform, confirm the reputation of the highly qualified developers of the "pipe". The answer now very much resembles a typical arrow transfer (forgive me for my Phranusian).

Ok, on Monday we'll ask for the logs for these transactions ourselves and post the result of the checks. Of course, if Mikalas does not mind.

CG      0       21:16:51.370    Trades  '': buy limit 5.00 ED-3.15 at 1.2405
FO      0       21:16:51.439    Trades  '': buy limit 5.00 ED-3.15 at 1.2405 placed for execution in 68 ms
QL      0       21:16:51.478    Trades  '': modify order #8393545 buy limit 5.00 ED-3.15 at 1.2405 sl: 0.0000 tp: 0.0000 -> 1.2492, sl: 0.0000 tp: 0.0000
MR      0       21:16:51.532    Trades  '': modify order #8393545 buy limit 5.00 ED-3.15 at 1.2405 sl: 0.0000 tp: 0.0000 -> 1.2492, sl: 0.0000 tp: 0.0000 placed for execution in 53 ms
OG      0       21:16:51.628    Trades  '': cancel order #8393545 buy limit 5.00 ED-3.15 at 1.2492
KR      0       21:16:51.672    Trades  '': cancel order #8393545 buy limit 5.00 ED-3.15 at 1.2492 placed for execution in 44 ms
PL      0       21:21:54.239    Trades  '': buy limit 5.00 ED-3.15 at 1.2405
OG      0       21:21:54.629    Trades  '': buy limit 5.00 ED-3.15 at 1.2405 placed for execution in 388 ms
RE      0       21:21:54.650    Trades  '': modify order #8393602 buy limit 5.00 ED-3.15 at 1.2405 sl: 0.0000 tp: 0.0000 -> 1.2498, sl: 0.0000 tp: 0.0000
HH      0       21:21:54.769    Trades  '': modify order #8393602 buy limit 5.00 ED-3.15 at 1.2405 sl: 0.0000 tp: 0.0000 -> 1.2498, sl: 0.0000 tp: 0.0000 placed for execution in 118 ms
KN      0       21:21:54.788    Trades  '': cancel order #8393602 buy limit 5.00 ED-3.15 at 1.2498
NJ      0       21:21:54.906    Trades  '': cancel order #8393602 buy limit 5.00 ED-3.15 at 1.2498 placed for execution in 118 ms
OE      0       21:26:55.771    Trades  '': buy limit 5.00 ED-3.15 at 1.2405
RL      0       21:26:55.849    Trades  '': buy limit 5.00 ED-3.15 at 1.2405 placed for execution in 77 ms
CN      0       21:26:55.880    Trades  '': modify order #8393659 buy limit 5.00 ED-3.15 at 1.2405 sl: 0.0000 tp: 0.0000 -> 1.2500, sl: 0.0000 tp: 0.0000
LL      0       21:26:55.968    Trades  '': modify order #8393659 buy limit 5.00 ED-3.15 at 1.2405 sl: 0.0000 tp: 0.0000 -> 1.2500, sl: 0.0000 tp: 0.0000 placed for execution in 87 ms
FE      0       21:26:55.996    Trades  '': cancel order #8393659 buy limit 5.00 ED-3.15 at 1.2500
OP      0       21:26:56.059    Trades  '': cancel order #8393659 buy limit 5.00 ED-3.15 at 1.2500 placed for execution in 63 ms
 
Renat:

Ok, we will ask for the logs for these transactions ourselves on Monday and will post the result of the checks.

Thank you for your understanding! To dispel the suspicions of MT5 sceptics on latency, it would be useful to provide statistical data on execution speed with a certain periodicity. Give a graph of the latency distribution minus the double ping.

I suggest that everyone who is longing to develop a single open-source parser of MT5 logs that would collect statistical data on specified dates for analysis. And share these statistics publicly in a separate thread. By working together we may be able to solve many delicate problems.

 
Renat:

Ok, on Monday we will ask for the logs for these trades ourselves and will publish the result of the checks. Of course, if Mikalas does not mind.

Of course I don't mind, I am a very interested trader (listing of 20.11.2014).

Only how will we check, because in OrdersLog there is the time of placing the order by the exchange and not the time of its receipt.