75,000 options - 4GB RAM and 4GB disk cache not enough??? - page 2

New comment
 
Yes, and before the entire disk pagingfile could be uploaded, the programme quietly crashed itself.
 
And to see all about the memory you have to swipe the picture to the right - the resolution is 2096x1200
 
Try on the latest build 197 (not from September 12): http://www.metatrader4.com/files/mt4setup.exe

sane, unfortunately you never gave a script and description for repeating the test. Well you don't want to do it because you came for something else?
Waste of time on the background of useless statements.
 
Renat:
Try on the latest build 197 (not from September 12): http://www.metatrader4.com/files/mt4setup.exe

sane, unfortunately you never gave a script and description for repeating the test. Well you don't want to do it because you came for something else?
Waste of time on the background of useless statements.
I downloaded the latest version of MT.
The picture is the same ...
 
Renat писал (а):
Try on the latest build 197 (not from September 12): http://www.metatrader4.com/files/mt4setup.exe

sane, unfortunately you never gave a script and description for repeating the test. Well you don't want to do it because you came for something else?
Waste of time on the background of useless statements.

No. I told you and showed you - e-asclose all adjustable parameters from 1 to 200 in intervals of 1
I'll send you the EA if you don't have it.
I came in order to use the tester of the program that I like (mq4), and what do you mean?
 
emailed. <br / translate="no">
installed a new terminal on a new computer i.e. took the mother out of the box, plugged the CPU, memory, power, installed the windup on the new drive. installed the terminal by the link.

Now the memory is DDR2 - everything is much faster)

already 1.5g allocated. about to burst. wait for it
 
Mak:
Renat:
Try on the latest 197 build (not from September 12): http://www.metatrader4.com/files/mt4setup.exe

sane, unfortunately you still haven't given a script and description for repeating the test. You don't want to do it because you have come for something else?
Waste of time on the background of useless statements.
I downloaded the latest version of MT.
Same picture...
At your specified limits it would be 57,629,880,000 (57 billion) runs. Not even our pessimistic calculation of required memory can help for that. Of course, we allocate memory tens/hundreds of times less than is required for a full run, but there's a complete baffle here. No matter how much you reduce, 57 billion is 57 billion.

The tester is designed to try limits from 1 to 2^31-1 (2 billion) - that's what it's optimised for. Putting out meaningless limits is not a normal use of the tester. We will add checks and not allow tests to run at obviously insane limits.

After all, this is a 32 bit system...
 
Renat писал (а):
[skipped] При указанных Ваших пределах будет 57 629 880 000 (57 млрд) прогонов [skipped]

What about me? I have 75000 or so.
And in my opinion, the number of runs can of course be limited to 2 yards (better to write the total number at the bottom of optimization parameters input form, so as not to count on a calculator or not to run a tester to see how many you get), but here it is clearly something else. it just does not release something somewhere.
By the way, I've checked the muxemple - there's nothing wrong with the memory. - And on the terminal downloaded from pfg with the same build the muxemple is not calculated at all. press start - there again start results -0. the parameters are the same.
 
sane, we will post a corrected 197 build today. Please try again. We changed the memory allocation algorithm
 
An updated build 197 has been posted: it has also "trimmed" the actual memory allocation in severe cases. But there's no way to pull out 57 billion.

sane, download the updated 197 build and try again, please.
12345678
New comment