
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
Anton:
Running your EA on Idle-CPU, RannForex-Server, 6 charts with different symbols. When I got back to my computer I saw a lot of these.
I have a bad time condition like that.
ZZY I attached the code for objectivity on the part of forum members.
Running your EA on Idle-CPU, RannForex-Server, 6 charts with different symbols. When I got back to my computer I saw a lot of this.
If I understood correctly, in this test there are 6 looped EAs running on 4 CPU cores, and each one is trying to load one core 100%. I.e. this is definitely a stress test, very far from normal operating conditions.
Under such conditions 1 or 2 ejections of 1-2ms for 10 million queries is an excellent result.
And once again, let me remind you: the greater the load, the more you test the efficiency of the OS task scheduler, not the terminal. Do not be fooled.
I have a question about the relevance of the ticks given by SymbolInfoTick.
Situation:
1. We do TimeCurretn(); we get time 18:00:00
2. Do SymbolInfoTick on an unlabeled symbol. We get a tick with the time 17:58:00.
3. Sleep(1)
4. Add SymbolInfoTick for the non-left symbol. We get a tick with the time 17:59:00.
I.e., in the fourth item we have a new tick, which is one minute different than TimeCurretn().
Do you see a problem in this situation?
How to get into this situation more rarely?
Test EA.
I don't have Alertite. Result (ran it on six charts).
There is a problem. It's hard to say how serious it is.
If I understand correctly, in this test there are 6 looped EAs running on 4 CPU cores, and each one is trying to load one core 100%. I.e. this is definitely a stress test, very far from normal operating conditions.
Is this EA a stress test? I'm asking you this because it's been measuring
is giving out a sea of Alerts.
There is a bug in ArrayPrint's serial log output.
It is clear that this is an error, since this is the source code.
Forum on trading, automated trading systems and strategy testing
MT5 and Speed in Action
fxsaber, 2020.10.30 15:04
I have Alert triggered every second many times.
19 ms and 48 ms for the execution of SymbolInfoTick. There were several dozens of cases where the duration was hundreds of microseconds. But I didn't cite them.
Apparently, in order to reproduce it, we need to run combat advisors for 24 hours, and then only watch. In my opinion, it is unrealistic to figure out what initiates such lags.
Looked at the Test9 code at the top of the page. Why 10 million times without any Sleep to request ticks from one symbol ? What does this test have to do with real trading?
I think the test should look like this: We request tick from each symbol in market review. We pause Sleep(1) and so on. Slightly rework your code:
Test 55 symbols in the overview.
Now let's test temp++ instead of SymbolInfoTick;
Looked at the Test9 code at the top of the page. Why 10 million times without any Sleep to request ticks from one character ?
Not at all. Read the branch for details.
Not on a level playing field. Read the thread for details.
Aren't you confused by the fact that even temp++'s maximum execution time takes tens of microseconds, with this metering technique ?