![MQL5 - Language of trade strategies built-in the MetaTrader 5 client terminal](https://c.mql5.com/i/registerlandings/logo-2.png)
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
The reason for SymbolInfoTick's braking seems to be parallel handling.
Result (inAmount = 15).
> 100 ms for SymbolInfoTick execution. It's clear that the code is self-shot. But it shows the reason why slows down on usual Expert Advisors.
Forum on trading, automated trading systems & strategy testing
MT5 and Speed in Action
Roman, 2020.10.14 04:54
Predefined variables, for the current tick, would be better.
Result (inAmount = 15).
HFT cannot be built with such delays.
Wouldn't it be better to take the tiki out of the glass?
Didn't measure it ?
Z.u.s. or better yet FIX it ))
It is better not to identify a new tick through the bars.
Result.
Bars lagging behind the actual state by seconds! Hello bar and indicator lovers.
It's extremely hard to call that a self-shot.
Result (inAmount = 15).
How do you do this?
20 charts.
Build 2656.
Ahh, was there 1000 queries there?
Just not at the computer to check.
fxsaber, and really why would there be 1000 queries for the current tick?
Anton, but it still slipped 19 mcs.
As a percentage of the rest, it's 850%
Roman:
Anton, but it still slipped 19 mcs.
As a percentage of the rest, it's 850%.
Sometimes the metering itself is slow, i.e. ::GetMicrosecondCount().
A simple example:
20 charts.
GetLastError() is just reading a memory cell in the nativa. Actually about zero cost.
If you still have doubts, you can do it this way:
This is something to keep in mind when evaluating the measurement of one-off actions through this benchmark.
A more accurate way of measuring:
20 charts.
Build 2656.
Sometimes the metering itself is slow, i.e. ::GetMicrosecondCount().
A simple example:
20 charts.
GetLastError() is just reading a memory cell in the nat. Actually about zero cost.
Thanks, I see.
But maybe still consider introducing predefined variables?
Reading a variable would probably be faster than calling a function and filling a structure.
A more accurate way of measuring:
Average hospital temperature.