![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
No transactions were made at this point.
ZS It's not uncommon.
PS In combat mode, when transactions are made, there are almost always lags (I only output cases greater than 5 milliseconds).
Otherwise seems to be much better than 2470.
Stats accumulated. HistorySelect lags only when making transactions.
ZS Lies. Without transactions, too, there are lags.
Put a lot of checks on it... Surprised by this.
Turns out to be a frequent occurrence. Trading functions have not been called.
SymbolInfoTick is not a bad lag sometimes. HFT may be very experienced with such unexpected lags.
Please ask the Developers to find the reasons. In the meantime, it is obvious that in combat EAs their profiler is a must.
Turns out to be a frequent occurrence. Trading functions have not been called.
SymbolInfoTick is not a bad lag sometimes. HFT may be very experienced with such unexpected lags.
Please ask the Developers to find the reasons. In the meantime, it's obvious that in battle EAs their profiler is a must.
How do you measure milliseconds with such accuracy? A hardware clock in your processor?
How do you measure milliseconds with such precision? A hardware clock in the processor?
GetMicrosecondCount().
Turns out to be a frequent occurrence. Trading functions have not been called.
SymbolInfoTick is not a bad lag sometimes. HFT may be very experienced with such unexpected lags.
Please ask the Developers to find the reasons. In the meantime, it is obvious that in battle EAs own profiler is a must.
the system timer has a 20ms step by default. did you reset it to a lower setting before the measurement?
you can try with functions like this:
The system timer has a default step of 20ms. did you reset it to a smaller step before measuring?
To the developers.
Forum on trading, automated trading systems and strategy testing
MT5 and speed in battle
Anton, 2020.05.29 12:32
The test code should look like this:
Please do not theorise any more. This is a practical application branch.
To the developers.
so this is the developers' response from several years ago.
so this is the developers' response from a few years ago.
Is it okay that the date is 2020.05.29 12:32
Is it OK that the date is 2020.05.29 12:32
I was wrong, fxsaber pointed it out: GetTickCount() can screw up like I wrote, but GetMicrosecondCount() cannot.
https://www.mql5.com/ru/forum/189360#comment_4838735
I'll keep silent from now on :)