Miracles with the tester. - page 3

New comment
 
notused:
Passes results do not match for optimization and single pass (service-desk - #329165 + EA in the same place)
Let's figure it out.
 
notused:
Optimisation and single pass results do not match (service-desk - #329165 + EA there as well)
Build 619? This problem has also begun to occur. But not always. Sometimes the results are even the same, i.e. no new optimization has been done, but the testing results are somehow different. For instance, the final profit in the chart differs from the one in the list. After some time everything is restored. I never noticed this before build 619 .
 
tol64:
Build 619? The same problem has started to occur. But not always. Sometimes the results are even the same, i.e. I haven't performed any new optimization, but I get different results during testing for some reason. For instance, the final profit in the chart differs from the one in the list. After some time everything is restored. I have never noticed this before build 619 .
The build 607 (have not updated to the new FIBO yet). Maybe the problem is in multicurrency and timer (OnTick() is not used), but not sure.
 
notused:
The build is still 607 (haven't updated to the new FIBO yet). Maybe the problem is multicurrency and timer (OnTick() is not used), but not sure.
Then the name for the branch is chosen accurately. Miracles with the tester. )))
 

Something is wrong with the latest build of the strategy tester. Suddenly (not "suddenly", but after the update to the 619 build) the Expert Advisor has practically stopped testing (the same as in application #329165) - it started consuming memory immensely (the "All ticks" mode for 5 years):

The last column is "VM size". As you can see I have 4 cores + 4 "remote" local agents (always worked fine).

At the same time the system starts lagging very badly (yup, 4GB RAM + 16GB dedicated for PageFile) and optimization speed tends to infinity. As you can see, CPU time, practically not engaged.

At the same time there are errors in the log:

This is apparently due to lack of memory.

I press "stop" - memory is not released immediately. In 5 minutes local agents disappeared, in another two minutes, memory of remote agents was freed:

Only not clear why one agent still have more than 100Mb hang (I do not believe that it took Cloud - because CPU time is not used).

Well, I disable "remote" local agents. Nothing changes (system lags and errors).

Well, I think, the error is in my Expert Advisor. Therefore I start testing a standard ExpertMACD, EURUSD, h12 from 2007.09.01 to 2012.03.26.

И... Same picture - lags, crazy memory usage (almost the same values as in the first picture) + "cannot initialize expert".

In both cases, some passes nevertheless succeed.

Log attached.

Very interesting lines:

CJ      0       local4  17:42:32        USDNOK: history synchronization started
QL      0       Core 1  17:42:33        USDNOK: history synchronization started
RK      0       local4  17:43:49        USDNOK: history downloading completed
GL      0       Core 1  17:43:49        USDNOK: history downloading completed
NM      0       Core 1  17:43:49        USDNOK: history for 2006 year synchronized
QJ      0       local4  17:43:49        USDNOK: history for 2006 year synchronized

etc. with USDNOK - in my EA one SGDJPY symbol was stitched in the code - why download USDNOK (USDJPY was successfully uploaded according to logs), instead of USDSGD?

If anything, the server is FIBOGroup-MT5 server.

P. S. I didn't see such problems in previous builds.

P. P. S. Please, check optimization of the standard ExpertMACD for the last 5 years on all ticks.

Files:
20120326.log  33 kb
 
notused:

Something is wrong with the latest build of the strategy tester. Suddenly (not "suddenly", but after update to build 619) EA has practically stopped testing (the same as in application #329165) - memory starts consuming an enormous amount (the mode "All ticks" for 5 years):

The last column is "VM size". As you can see I have 4 cores + 4 "remote" local agents (always worked fine).

The system starts to slow down very horribly (yup, 4GB RAM + 16GB given away for PageFile) and the optimization speed tends to infinity. As you can see, CPU time, practically not engaged.

It is not recommended to run more agents than there are cores. Excessive number of agents causes speed to drop non-linearly and resource consumption to grow. Especially when there is only 4 Gb of memory and agents eat up a gigabyte or more.

Do not install remote agents on the same computer where you work with the terminal.


There are errors in the log:

It must be due to lack of memory.

I press "stop" - memory is not freed at once. In 5 minutes local agents disappeared, in another two minutes remote memory is freed:

Yes, memory (caches) are freed after about 5 minutes. They are purposely kept for the next run, so that time is not wasted warming up most often the same data that was used on the last run.

In the latest build we've changed the way we handle caches, which has increased them for the sake of speeding up re-runs.


It's just not clear why one agent has more than 100Mb hanging around (I don't believe it was used by Cloud, because CPU time is not used).

Well, I disable "remote" local agents. Nothing changes (system lags and errors).

Well, I think, the error is in my Expert Advisor. Therefore I am testing a standard ExpertMACD, EURUSD, h12 from 2007.09.01 to 2012.03.26.

Have you recompiled the Expert Advisor after upgrading to the latest build?

In your case the problem is in slowdowns due to constant swapping and lack of memory. Advice: Disable unnecessary remote agents.

 
Renat:

It is not recommended to run more agents than there are cores. Excessive number of agents causes speed to drop non-linearly and resource consumption to increase. Especially when there is only 4 Gb of memory and agents are eating up a gigabyte or more.

You can look at the Cloud stats - whether 4 or 8 agents - PR is still around 150-190 (except one/two, which apparently fall on the browser core)
Renat:

Do not install remote agents on the same computer where you do your main work with the terminal.

Disabled remote agents...
Renat:

Did you recompile the EA after upgrading to the latest build?

In your case the problem is in slowdowns due to constant swapping and lack of memory.

Experts recompiled. Even the regular ExpertMACD recompiled.
Renat:

A word of advice: disable unnecessary remote agents.

I disabled it, ran ExpertMACD for optimization and:

GS      2       Core 2  22:35:03        genetic pass (14, 128209952076) tested with error "cannot initialize expert"
JD      2       Core 2  22:35:47        genetic pass (18, 83657327618) tested with error "cannot initialize expert"
HK      2       Core 1  22:35:55        genetic pass (21, 125407780989) tested with error "cannot initialize expert"
PN      2       Core 2  22:36:31        genetic pass (23, 119213797642) tested with error "cannot initialize expert"
DQ      2       Core 2  22:36:31        genetic pass (24, 69556992446) tested with error "cannot initialize expert"
PE      2       Core 3  22:36:35        genetic pass (27, 43810326828) tested with error "cannot initialize expert"
EI      2       Core 3  22:37:15        genetic pass (31, 50607133818) tested with error "cannot initialize expert"
MM      2       Core 3  22:37:15        genetic pass (33, 154340017542) tested with error "cannot initialize expert"
OR      2       Core 3  22:38:10        genetic pass (39, 72154186657) tested with error "cannot initialize expert"
RE      2       Core 3  22:38:53        genetic pass (44, 3365963874) tested with error "cannot initialize expert"
NJ      2       Core 3  22:38:53        genetic pass (45, 69101442583) tested with error "cannot initialize expert"
JO      2       Core 3  22:38:53        genetic pass (46, 13607620667) tested with error "cannot initialize expert"
JS      2       Core 1  22:40:24        genetic pass (53, 86662534982) tested with error "cannot initialize expert"
ID      2       Core 1  22:40:24        genetic pass (54, 101351711755) tested with error "cannot initialize expert"
HG      2       Core 1  22:40:24        genetic pass (55, 121960550013) tested with error "cannot initialize expert"

And now disabled all agents (including local agents) except one:

IR      2       Core 1  22:44:22        genetic pass (1, 59037561933) tested with error "cannot initialize expert"
GE      2       Core 1  22:44:56        genetic pass (3, 122174849602) tested with error "cannot initialize expert"

and now what? 4GB is not enough for one agent? (although Mem Usage is 350MB, VM Size = 1.24GB). What about those who don't even have 4GB?

Why don't you check? See previous post for replay steps.

 
notused:
You can look at the Cloud stats - either 4 or 8 agents - PR is still in the region of 150-190 (except one/two, which apparently fall on the browser core) Disabled remote agents... Experts recompiled. Even the regular ExpertMACD recompiled.

Disabled, ran ExpertMACD for optimisation and:

Now disabled all agents (including local agents) except one:

and now what? 4GB is not enough for one agent? (although Mem Usage is 350MB, VM Size = 1.24GB).

Why don't you check it after all? The reproduction steps are in the previous post

It was enough to look at EA's log to see the errors:

ExpertMACD (EURUSD,H1)  22:50:54        1971.01.05 00:00:00   CExpertBase::InitHigh: error initializing object
ExpertMACD (EURUSD,H1)  22:50:54        1971.01.05 00:00:00   OnInit: error initializing indicators

ExpertMACD (EURUSD,H1)	22:55:07	2012.01.01 00:00:00   CSignalMACD::ValidationSettings: slow period must be greater than fast period
ExpertMACD (EURUSD,H1)	22:55:07	2012.01.01 00:00:00   OnInit: error signal parameters

Choose correct time period and correct settings. If you use default limits, you can generate a lot of wrong settings.

 
Renat:

It was enough to look at the EA log to see the errors:

Choose the right time period and the right settings. If you use default limits, you may generate a lot of wrong settings.

Yes, indeed, the problem turned out to be in the default parameters. I changed them - everything is testing fine. I returned to my Expert Advisor - so far it seems to be "flying normally".

So, if earlier the availability of two agents per kernel was forgiven, now it is definitely not.

Bottom line2. Was wrong, sorry for the time taken (but service-desk - #329165 has not figured it out yet)

 
stringo:
We'll figure it out.

It's taking a long time. In the meantime, I found out what's wrong.

1) While refactoring the code, I lost explicit assignment of the variable value and sometimes (quite randomly) received random results for the opened position volume. Having fixed this error, I saw that the results didn't change - the test results didn't coincide with optimization. Various logging and tambourine tricks helped us find out that the problem is quite old:

2) Before the start of the Championship-2011, I reported that the tester makes deals on weekends. Renat promised to check it. But the problem remains to this day. Completely by accident, I chose the beginning of the testing interval 2007.09.01, which is a weekend. So, the optimizer does not perform a trade on this day but the tester does. To be more precise, it does not reach OrderSend in the optimizer on weekend, but it does in the tester. Judging by the logic of my Expert Advisor, I managed to find out that if the optimization period starts at weekend, ACCOUNT_EQUITY = 0 when the timer first goes off!!! In the tester, ACCOUNT_EQUITY = ACCOUNT_BALANCE (that is what we set in the initial deposit). If the beginning of the optimization period falls on a business day, then the behavior of optimizer and tester are identical.

So, you have two bugs:

1) The optimizer allows you to open a deal on a weekend, which should not be (and do not say that this is my error - I will correct my mistakes, while the tester's bug has been hanging for more than half a year);

2) When timer first triggers, if beginning of period falls on output, ACCOUNT_EQUITY = 0, while in tester ACCOUNT_EQUITY = ACCOUNT_BALANCE. We need to bring it to the same form (better, of course, to ACCOUNT_EQUITY = ACCOUNT_BALANCE with correction of the first error).

In service-desk on request #329165 I will attach an expert for tests.

1234567
New comment
Reason: