
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
And the fact that I'm slow is confirmed by the fact that even this doesn't play for anyone else:
Now I've tried it - it's not playing for me either. Perhaps the principle of calculations on the weekly and monthly chart with deep history has changed and the delays have disappeared by themselves
Yes, that's why I use this condition in mqh.
on the first check false kills the other 4 checks. it is better to use || then, the subsequent ones will be ignored in case of lags.
on the first check false kills the other 4 checks. it is better to use || then, the subsequent ones will be ignored in case of slowness.
This is the way it's meant to be. If GetMicrosecondsCount is slow, it is always slow.
Please share the results of running this EA from your VPS (not your home machine).
Not really a VPS, but a virtual machine on rented hardware:
Not really a UPU, but a virtual machine on rented hardware:
Thank you. On your machine, the braking seems to be weak. You would need to change the FreezeVPS condition to a suitable one so that such a configuration is not considered slow.
Please share the results of running this EA from your VPS (not your home machine).
It just quit twice and then it's gone, it won't run again.
I don't know how to interpret it.
And on a local virtual machine, this
Please share the results of running this EA from your VPS (not your home machine).
1 core, 1GB RAM.
No timings shown. I didn't look into the code, I compiled it as is.
No timings were shown. I didn't look into the code, I compiled as is.
Thanks for the information. In Benchmark.mqh the top line should be uncommented and the bottom line the other way around. So that it would be like this.
Then the metering will work. Now we have a protection, that if "brakes" are detected, then do not measure.
Thanks for the information. In Benchmark.mqh you need to uncomment the top line and reverse the bottom line. So that it is like this.
Then the metering will work. Now there is a protection, that if you find "brakes", then do not measure.
Thanks for the batch. Yes, the LAN alerts very often.
Now I understand how to interpret it.
The FreezeVPS condition will have to be changed to a suitable one so that it is not considered a bottleneck.
Based on the measurements you posted, I have made the appropriate adjustments.