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
Forum on trading, automated trading systems and trading strategy testing
MT5 and Speed in Action
fxsaber, 2020.10.07 11:13
Can't check how it will be on slow VPS.
If you do any printouts after OrderSend (e.g. order sending result), it's better to accumulate them in a string-variable, and send it to print on exit from On-function.
Otherwise, you may lose a lot of money connecting to a Print-snapshot. How much - you can answer, if someone runs the above advisor on his VPS.
ZZZ The simplest implementation.
On a fast machine this solution is much faster than the usual approach. How on VPS - don't know.
If you make any printouts after OrderSend (e.g. order sending result), it is better to accumulate them in a string-variable, and send it to print on exit from On-function.
Otherwise, you may lose a lot of money connecting to a Print-snapshot. How much - you can answer, if someone runs the above advisor on his VPS.
On my $3 VPS
On my $3 VPS.
Thank you. Definitely a better workaround.
It is more expensive to send to someone else's chart than to your own.
Try it this way:
Try it this way:
Result.
When metering is switched off.
I.e., it takes less than 10µs to switch to "OnEmpty".
Why not do the same for zero?
I.e. it takes less than 10µs to switch to "OnEmpty".
Why not do the same for zero?
Different meaning and different execution mechanism. 0 - event to "own" chart. -1 - event in own chart queue.
Forum on trading, automated trading systems and trading strategy testing
MT5 and Speed in Action
fxsaber, 2020.10.07 12:41
I've never tried to use TimeCurrentMsc in MQL5, despite my repeated requests.
Will it be?
Different meaning and different execution mechanism. 0 is an event in the "own" chart queue. -1 - event in own queue.
It turns out, that through -1 asynchrony of the same Alert cannot be implemented.
This means that it takes less than 10 microseconds to switch to OnEmpty.
As you can see with your help everything was solved faster than the most optimistic predictions, it turned out that there is a hidden backdoor
Will there be?
Not quite the same, but a counter by mcs interval.
YesTimeCurrentMcs wouldbe better, I join the wish.