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
In 10 years on minutes, one buffer is calculated to take up 28 mb.
In the five-minute periods, 5 mb.
On fifteen minutes, 2 mb.
Is there a problem?
Andrei01:
А в чем причина?
Single-threaded code execution.
Also, the reason can be attributed to the addition of additional checks, which are automatically made in the indicator using a simple variable prev_calculated, different behavior of global variables, visualization capabilities.
Have the developers deliberately put brakes on complex calculations in the Expert Advisor?
All the favourites are gone.
All the subscription ticks in the profile are gone.
Maybe it's neater to update the site somehow? It's not the first day we've used it...
All the favourites are gone.
All the subscription ticks in the profile are gone.
Maybe it's neater to update the site somehow? It's not the first day we've used it...
1. single-threaded code execution.
2. also to the reason we can add additional checks, which in an indicator are done automatically by simple variable prev_calculated, different behaviour of global variables, visualisation possibilities.
1. So indicators allow multi-threaded calculations?
2) What is the problem with making these checks in an Expert Advisor?
If complex calculations kill the expert, those calculations will also kill the indicators. This is not an argument. The time saving is in the multithreading of indicators, but it is a waste of memory. The Expert Advisor works in a sequential thread. And here we have some doubts that the multi-threading of indicators will give a sufficient gain in time in comparison with in-expert calculations. But in case of calculations inside the Expert Advisor we will save memory. That is significant when EAs participate in the Championship. The Organizers paid much attention to your Expert Advisor at the previous Championship because it consumed much memory. That is why it was pulling all those checks and unnecessary history. (iCustom();)
1. so indicators allow multi-threaded computing?
2. what is the problem with doing these checks in EA?
The clownery continues! pAtAmUshT the Expert Advisor is one thread, and each indicator can be in its own thread if there are enough cores.
Show us how easy it is for you to make multiple threads in EA?
If complex calculations kill the expert, those calculations will also kill the indicators. This is not an argument. The time saving is in the multithreading of the indicators, but it is a waste of memory. ...................
Can you give me an example of code?
Show us how easy it is for you to make multiple threads in an EA?