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
Most likely after the next release version (now in beta)
Most likely after the next release version (now in beta)
Won't there be an array of deals?
Forum on trading, automated trading systems and trading strategy testing
MT5 and Speed in Action
fxsaber, 2020.08.13 04:36
This ancient script shows many brakes if you run it on one MQ-Demo chart and add more trading symbols to Market Watch (I had 100).
Terminal Log.
2020.09.04 17:51:33.112 Trades '34510052': cancel order #702851395 buy stop 0.01 EURCAD at 1.55852 2020.09.04 17:51:33.512 Trades '34510052': accepted cancel order #702851395 buy stop 0.01 EURCAD at 1.55852 2020.09.04 17:51:33.514 Trades '34510052': cancel #702851395 buy stop 0.01 EURCAD at market done in 401.845 ms
The deletion of the pending trade occurred in 401ms. The developers have access to the trading server logs and can see how long the execution lasted there. For example.
Everyone can reproduce it on their site.
Just in case, this is what a trade order with results looks like.
Ping.
The script worked for about 10 minutes.
I don't care about these slowdowns. I just want to know where and what I can adjust to improve the situation. Is it the Terminal or the trading server? In general, the developers have all possibilities to reproduce and, if desired, to understand.
This ancient script will show many brakes if you run it on a single MQ-Demo chart and add more trading symbols to Market Watch (I had 100).
I remember this case
Forum on trading, automated trading systems and strategy testing
New version of MetaTrader 5 platform build 1880: Calculation of full synthetic instrument history
A100, 2018.07.25 21:55
The load needs to be taken into account in any case:
I have a slow computer... and I have a very slow one... So... If I add 63 symbols in Market Watch and press F10 after that, MetaTrader hangs hard (has to restart)... while in all other modes it works fine
I tried to use F10 but it kept on hanging for at least a year - although it was on 32 bit version
I remember a case like this
The number of characters in the Market Review is not crucial to playing brakes. It's just the way I've done it in mine.
It's easy to reproduce. There is only 1ms between the two red local times, which should actually be 550ms (consecutive OrderSend). Apparently, Print-snapshots have an effect here too.For the sake of your position, any self-shooting is in order?
Result on b2592 MQ-Demo.
There is a lag on every call.
Forum on trading, automated trading systems and trading strategy testing
Bugs, bugs, questions
A100, 2020.08.31 15:55
I have a very good timeframe, especially for EURUSD, crosshair moves very slowly following the cursor, it is enough to move the cursor smoothly diagonally to reproduce it. It is OK in other timeframes. There was no such delay before
And all manual plotting (trend, Fibonacci, etc.) is also slow
All settings are by default:
12797
Some kind of inverse dependence: the less bars, the slower
On monthly and weekly charts for example EURGBP (where there is no such deep history) - no delays
Some kind of inverse relationship: the lower the bars, the slower
Rather, it is direct - the higher the TF, the longer the delay.
Apparently, this is due to precise calculation of coordinates by the lower TF. Somewhere messed up with getting the indices of the bars included in the weekly/monthly bar we're looking for.
ps: everything works for me, same number of bars
More like a straight line - the higher the TF, the greater the delay.
Apparently, due to accurate calculation of coordinates on the lower TF. Somewhere they messed up with getting indices of bars included in the required weekly/monthly bar.
ps: everything works for me, same number of bars
Naturally, no experts/indicators/scripts are running - only manual builds. The latency indicated is reproducible on any average modern 64-bit tablet. If you have an i7 computer, I assume you haven't encountered this delay
I probably should have specified that a tablet was being used.
I have an i5