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 so:
?
I have accelerated it by a factor of one and a half.
Zero (in your case "coefficient") is just as stupidly chosen (almost "out of the blue").
// As a potential user, I suggest that you still think carefully about this point.
// I have reasonable thoughts on the subject, we can discuss it at our leisure.
If you put 1.1 instead of 1 when calculating zero, the results (numeric, not speed) will be exactly the same as in your case.
Is such a question https://www.mql5.com/ru/forum/6343/page5#comment_177533 appropriate in this thread?
1. Accelerated by a factor of one and a half.
2. have reasonable thoughts on the subject, can be discussed at leisure.
1. good solution, thanks. The gist is the same as mine, but you've done with one marking array instead of two - hence the speed gain. Looks like you couldn't do any better.
Unless you take the markup out of the loop:
:)
2. Sure.
Is such a question https://www.mql5.com/ru/forum/6343/page5#comment_177533 appropriate in this thread?
And like this...
The input is an array with sector sizes( nosorting of the array is required).
Why you have a negative number in the array there - I don't understand. Probably sector partitioning?
Good solution, thanks. The idea is the same as mine, but you've made do with one marking array instead of two - hence the speed gain. Looks like you couldn't do any better.
The gain has been achieved by many small improvements. You can also speed up a little bit more "small stuff".
For example, if you reduce the second parameter by one beforehand when calling the roulette:
you still get a quite measurable difference.
But that's not all. The real "big win" is ahead. Wait, I'll debug it and post it.
// there is a small bug - already fixed.
And like this...
1. an array with sector sizes is input( nosorting of the array is required).
2. Why you have a negative number in the array there - I don't get it. Probably sector partitioning?
1. the problem is that the input is raw data. They just need to be converted into sector sizes as the game goes on. That's part of the problem. :)
2. No way. Just torture joo, he'll admit it if you push hard enough. I'm debugging now. ;)
You were not impressed by the result?
That's naive. ;) Increase the input array 10,000 times - then you're bound to be impressed.
--
I'm waiting for comparative tests // on large array.
;)
I'm waiting for comparative tests // on a large array.
Can't seem to wait... :)
I'll have to do it myself again:
At the same time I've combed it all in the class and put into CRoulette.Reset();