Looking for some information about built-in historical tester in jforex 3.2.19 demo

When I launch a test of strategy with custom period two years or more, I observe an effect of significant speed reduction of the historical tester after 30% of work completed.
The same effect I can notice on different modern powerful hardware configuration with different strategies.
Also the phenomena is present in jforex 3 for mac os and jforex for windows 10 system.
The first 20% of work was completed in 70 minutes. It took 16 hours to complete other 20% percent.
The test is still running.

Moreover, I have reports of this uncomfortable speed reduction from members of my team.
Could it be related to heap size ?

How many traders have encountered similar problem?
Could you suggest a solution of the problem?

Thanks!

Hardware configuration

CPU 3.8 GHz Intel Core i5
RAM 24 GB 2400 MHz DDR4
Video Radeon Pro 580 8192 MB
Storage 2.12 TB
Fusion Drive

MacOs 10.12.6


https://imgur.com/IK8M2tI

We will look into this

We suspect this is due to out of memory problem.

Please try to increase the Max heap size.
If you have installed JF, open "Advanced settings/Memory" to increase it.
If you launch it by webstart, edit the .jnlp file and change -Xmx in this line:

<java version="1.8+" java-vm-args="-Xmx512m -Xms32m"/>

Save and run it.

I will try the proposition. Hopefully, it helps to improve the performance of the Historical Tester. Thanks!

I have tried system max heap size and custom max heap size
The screen is https://i.imgur.com/CjV87GQ.png

There was no improvement in speed at all.
The historical tester did 15% work completed in two hours. Later, it was moving extremely slowly at 33% after 24 hours of work (two nightshifts)
The screen is https://i.imgur.com/lZr5Pl2.png

My team members also haven't observed any improvement.
I am ready to provide any log file if it can be useful in effective solution of the problem.

Do you have any information from your side about this anomalous speed reduction?

I can share the timeline of speed reduction.
Please, provide us with instructions.
How can we improve the speed of the Historical Tester?

Test Start @21:02:59 04.11.2018


Test after approximately 1Hours .50min. 14%.completed



Test after 9Hours 27% completed


Test after 20Hours and 30min 35% completed
ETA estimated time of arrival one day and 15 hours

We are looking into this. Can you confirm this problem on any strategy? If not, could you provide at least part of the code to repeat the issue?

Yes, we observe that reduction of speed of the Historical Tester with different strategies.
I am ready to provide the code.
Do you need vfs or jfx source?
Where can I submit the code?

.java code please.

Please send it to [email protected]
Subject: JForex Historical Tester

I have just sent the code and the value of parameters. Looking forward to the solution of this issue.

We have improved several things, which will solve the problem hopefully. Will be deployed soon.

I have problems with the tester API, which may be related to this behaviour. I posted it here: https://www.dukascopy.com/swiss/english ... 16&t=55622

Will this improvements solve my problem as well???

My team members have observed significant improvement of the Historical Tester's speed in 3.2.22

Strongly appreciate your support!

THANK YOU!