
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
Check out the new article: Developing a Replay System (Part 61): Playing the service (II).
In this article, we will look at changes that will allow the replay/simulation system to operate more efficiently and securely. I will also not leave without attention those who want to get the most out of using classes. In addition, we will consider a specific problem in MQL5 that reduces code performance when working with classes, and explain how to solve it.
In the previous article, Developing a Replay System (Part 60): Playing the service (I), we made some adjustments to enable the replay/simulator service to start generating new data on the chart. Although we made minimal changes to allow the system to begin launching data, it quickly became apparent that something unusual had occurred. Despite the absence of major modifications, the system seemed to have suffered a significant setback. This situation gives the impression that the system has become unviable, as it suddenly slowed down drastically. Is it really so? And if so, how can we resolve this issue? It is important to remember that we aim to keep everything aligned with object-oriented programming principles.
Although there was indeed a drop in performance, we can address most of this issue simply by understanding and properly adjusting certain aspects of the code. In this article, I may begin demonstrating how to use some of the tools available in MetaEditor, which greatly facilitate the process of refining and improving the code. In hindsight, I should have introduced this topic a few articles ago. However, I did not see the same level of necessity as I do now, when it is crucial to understand how the code operates and why its performance has degraded so significantly.
Author: Daniel Jose