Tester Build 2090 hat immer noch ein Speicherleck ( For Metaquotes: Memoryleak on Harddrive) - Seite 2

Neuer Kommentar
 

Das ist nicht das temp-Verzeichnis.

Hier werden wahrscheinlich die Dateien mit den Tickdaten erzeugt und wieder gelöscht.

 

Ebend gerade wieder aufgefallen.

Build 2095

Aber anderer Rechner.

Agent 7 und 1 hängen.

Laut log können sie nicht beendet werden und belegen knapp 10gb Ram.

Temp Ordner ist mit knapp 9gb pro Agent belegt.

ES      0       16:45:43.732    Tester  0ac6af11846dac0c (0, 6111) : passed in 0:00:00.446
FR      0       16:49:40.824    Network 3860 bytes of account info loaded
EK      0       16:49:40.824    Network 1482 bytes of tester parameters loaded
IO      0       16:49:40.824    Network 19132 bytes of input parameters loaded
EE      0       16:49:40.832    Network 17731 bytes of symbols list loaded
IM      0       16:49:40.832    Tester  job 6713531116306827294 received from Cloud Server
CI      0       16:49:40.832    Tester  file added, 130921 bytes loaded
ON      0       16:49:40.832    Network 23796 bytes of optimized inputs info loaded
NF      0       16:49:40.840    Tester  successfully initialized
EQ      0       16:49:40.840    Network 723 Kb of total initialization data received
MF      0       16:49:40.840    Tester  AMD Ryzen 7 1700X Eight-Core Processor , 49084 MB
MM      0       16:49:40.840    Tester  optimization pass 203 started
MG      0       16:49:40.864    Symbols GBPJPY: symbol to be synchronized
JS      0       16:49:41.835    Symbols GBPJPY: symbol synchronized, 3464 bytes of symbol info received
MG      0       16:49:45.504    History GBPJPY: load 27 bytes of history data to synchronize in 0:00:02.511
EI      0       16:49:45.504    History GBPJPY: history synchronized from 2015.01.02 to 2019.07.04
KP      0       16:49:45.705    History GBPJPY,M15: history cache allocated for 112493 bars and contains 24713 bars from 2015.01.02 00:00 to 2015.12.31 20:45
QR      0       16:49:45.706    History GBPJPY,M15: history begins from 2015.01.02 00:00
LO      0       16:49:54.583    Symbols EURJPY: symbol to be synchronized
PO      0       16:49:55.666    Symbols EURJPY: symbol synchronized, 3464 bytes of symbol info received
DR      0       16:49:56.574    History EURJPY: load 27 bytes of history data to synchronize in 0:00:00.907
DF      0       16:49:56.574    History EURJPY: history synchronized from 2015.01.02 to 2019.07.04
IG      0       16:50:07.742    Symbols EURGBP: symbol to be synchronized
JR      0       16:50:08.461    Symbols EURGBP: symbol synchronized, 3464 bytes of symbol info received
JD      0       16:50:09.374    History EURGBP: load 27 bytes of history data to synchronize in 0:00:00.707
FH      0       16:50:09.374    History EURGBP: history synchronized from 2015.01.02 to 2019.07.04
NS      0       16:58:02.202    Tester  tester agent shutdown started
GI      0       16:58:02.202    Tester  shutdown tester machine
FM      2       16:59:03.203    Tester  cannot stop tester process [0, 0]
KK      0       16:59:04.847    Network connected to agent1.mql5.net
CD      0       16:59:07.355    Network connected to agent2.mql5.net
FM      0       16:59:11.150    Network connected to agent1.mql5.net
QF      0       16:59:14.168    Network connected to agent2.mql5.net
EO      0       16:59:17.773    Network connected to agent1.mql5.net
CH      0       16:59:20.754    Network connected to agent2.mql5.net
FP      0       16:59:23.512    Network MQL5 Cloud Network server agent2.mql5.net selected after rescan (ping 165 ms)
CD      0       16:59:23.686    Network connected to agent2.mql5.net
KM      0       16:59:24.018    Network authorized on agent2.mql5.net for collider
IF      0       17:00:25.481    Network connected to agent2.mql5.net
CM      0       17:00:25.823    Network authorized on agent2.mql5.net for collider
 

Christian,

bei mir - aktuell läuft kein Auftrag - haben versch. tmp-Verzeichnisse 4,12 GB von 66 Dateien, alle mit derselben Größe:


Meine 12 Agenten liegen auf einer eigenen (kleinen) HD mit ~500 GB.

Ich spekuliere mal: 12 Agenten * 4GB  => ~50 GB, das wären 10% der Gesamtkapazität der HD.

Das Verzeichnis der Agnten insgesamt belegt 26GB.

Könnte es sein, dass sich auch bei Dir die TesterAgenten sich in dieser Form an der Gesamtkapazität Deiner HD orientieren?


Das wäre der Log zu diesen Dateien von 17.07.2019 16:52

FH      0       16:49:45.825    Network 3860 bytes of account info loaded
QQ      0       16:49:45.825    Network 1482 bytes of tester parameters loaded
ME      0       16:49:45.825    Network 19132 bytes of input parameters loaded
NP      0       16:49:45.827    Network 17731 bytes of symbols list loaded
EG      0       16:49:45.828    Tester  job 6713531116306827294 received from Cloud Server
KO      0       16:49:45.828    Tester  file added, 130921 bytes loaded
OH      0       16:49:45.828    Network 23796 bytes of optimized inputs info loaded
EP      0       16:49:45.831    Tester  successfully initialized
JH      0       16:49:45.831    Network 2985 Kb of total initialization data received
HQ      0       16:49:45.831    Tester  Intel Core i7-8700T  @ 2.40GHz, 65482 MB
OI      0       16:49:45.831    Tester  optimization pass 5168 started
FN      0       16:49:45.841    Symbols GBPJPY: symbol to be synchronized
IE      0       16:49:47.717    Symbols GBPJPY: symbol synchronized, 3464 bytes of symbol info received
ON      0       16:49:52.808    History GBPJPY: load 27 bytes of history data to synchronize in 0:00:05.092
GS      0       16:49:52.808    History GBPJPY: history synchronized from 2015.01.02 to 2019.07.04
HJ      0       16:49:52.991    History GBPJPY,M15: history cache allocated for 112493 bars and contains 24713 bars from 2015.01.02 00:00 to 2015.12.31 20:45
CL      0       16:49:52.991    History GBPJPY,M15: history begins from 2015.01.02 00:00
PF      0       16:50:00.209    Symbols EURJPY: symbol to be synchronized
LQ      0       16:50:01.021    Symbols EURJPY: symbol synchronized, 3464 bytes of symbol info received
MJ      0       16:51:56.220    History EURJPY: load 13.38 Mb of history data to synchronize in 0:01:55.236
QI      0       16:51:56.220    History EURJPY: history synchronized from 2015.01.02 to 2019.07.04
NM      0       16:52:04.746    Symbols EURGBP: symbol to be synchronized
QH      0       16:52:05.466    Symbols EURGBP: symbol synchronized, 3464 bytes of symbol info received
OQ      0       16:52:41.085    History EURGBP: load 12.48 Mb of history data to synchronize in 0:00:35.598
MR      0       16:52:41.085    History EURGBP: history synchronized from 2015.01.02 to 2019.07.04
KE      0       16:57:55.556    Tester  tester agent shutdown started
JO      0       16:57:55.556    Tester  shutdown tester machine
PG      2       16:58:56.556    Tester  cannot stop tester process [0, 0]
QR      0       16:58:58.049    Network connected to agent1.mql5.net
NK      0       16:58:59.903    Network connected to agent2.mql5.net
ED      0       16:59:07.857    Network connected to agent1.mql5.net
OM      0       16:59:10.616    Network connected to agent2.mql5.net
QF      0       16:59:18.855    Network connected to agent1.mql5.net
CO      0       16:59:21.953    Network connected to agent2.mql5.net
EI      0       16:59:29.289    Network MQL5 Cloud Network server agent2.mql5.net selected after rescan (ping 172 ms)
QK      0       16:59:29.466    Network connected to agent2.mql5.net
CG      0       16:59:29.819    Network authorized on agent2.mql5.net for gooly
LE      0       17:00:31.211    Network connected to agent2.mql5.net
OG      0       17:00:31.561    Network authorized on agent2.mql5.net for gooly
LR      0       17:01:32.943    Network connected to agent2.mql5.net
JF      0       17:01:33.307    Network authorized on agent2.mql5.net for gooly
 

Sehe in deiner Log die selbe Fehlermeldung.

Deswegen bestimmt auch die noch offenen *.tmp Dateien.

Glaube ich nicht das die sich an die Kapazität der Platte anpassen.

Auf dem Rechner mit der 256gb sind die Temp Daten viel größer gewesen.

Der andere hat 512gb

 

Ich kann nicht erkennen, ob das ein Fehler des Agenten ist, eine Fehler des optimierten Programms oder ob der 'Auftraggeber des Test abgebrochen hat.

Bei uns beiden stellt sich unser Rechen-Agent wieder zur Verfügung.

"Tester  shutdown tester machine" muss ja nicht unbedingt unser PC sein, vielleicht ist deren Wortwahl einfach ungeschickt.

Wie groß ist den das Verzeichnis \Tester\ (in dem bei mir alle 12 Agenten 'liegen')

 
Zusatzfrage, was für ein System verwendest Du, dass Du die Größe des temp-Verzeichnis beschränken kannst - oder hab eich das falsch verstanden?
 

Ja wäre möglich aber sehr unplausibel da die Log ja hier geschrieben wird.


Aktuell nix los aber Speicher belegt.

Knapp 25gb.

Hast du das schon irgendwo kommuniziert ?

 
Carl Schreiber:
Zusatzfrage, was für ein System verwendest Du, dass Du die Größe des temp-Verzeichnis beschränken kannst - oder hab eich das falsch verstanden?

Kann ich nicht, ich denke bei 24,1 gb ist die Grenze intern im Agent für das Temp Verzeichniss

 
Christian:

Kann ich nicht, ich denke bei 24,1 gb ist die Grenze intern im Agent für das Temp Verzeichniss

Bei mir ist das \temp\-Verzeichnis wieder leer - alle Dateien von oben sind jetzt weg. Allerdings habe ich einen neuen Job erhalten:

EI      0       16:59:29.289    Network MQL5 Cloud Network server agent2.mql5.net selected after rescan (ping 172 ms)
QK      0       16:59:29.466    Network connected to agent2.mql5.net
CG      0       16:59:29.819    Network authorized on agent2.mql5.net for gooly
LE      0       17:00:31.211    Network connected to agent2.mql5.net
OG      0       17:00:31.561    Network authorized on agent2.mql5.net for gooly
LR      0       17:01:32.943    Network connected to agent2.mql5.net
JF      0       17:01:33.307    Network authorized on agent2.mql5.net for gooly
JR      0       17:59:33.243    Network connected to agent1.mql5.net
CK      0       17:59:34.701    Network connected to agent2.mql5.net
KP      0       17:59:41.971    Network connected to agent1.mql5.net
KI      0       17:59:43.428    Network connected to agent2.mql5.net
CN      0       17:59:50.700    Network connected to agent1.mql5.net
MG      0       17:59:52.158    Network connected to agent2.mql5.net
OS      0       17:59:59.404    Network MQL5 Cloud Network server agent1.mql5.net selected after rescan (ping 22 ms)
CE      0       17:59:59.435    Network connected to agent1.mql5.net
GM      0       17:59:59.492    Network authorized on agent1.mql5.net for gooly
KH      0       18:01:00.835    Network connected to agent1.mql5.net
NL      0       18:01:00.888    Network authorized on agent1.mql5.net for gooly
MF      0       19:17:58.140    Network 3860 bytes of account info loaded
NM      0       19:17:58.140    Network 1482 bytes of tester parameters loaded
CH      0       19:17:58.140    Network 5820 bytes of input parameters loaded
QM      0       19:17:58.141    Network 928 bytes of symbols list loaded
QG      0       19:17:58.141    Tester  job 6713569350105707021 received from Cloud Server
JQ      0       19:17:58.141    Tester  file added, 51962 bytes loaded
CJ      0       19:17:58.141    Network 2748 bytes of optimized inputs info loaded
EO      0       19:17:58.599    Tester  successfully initialized
DD      0       19:17:58.599    Network 74 Kb of total initialization data received
JO      0       19:17:58.599    Tester  Intel Core i7-8700T  @ 2.40GHz, 65482 MB
PK      0       19:17:58.599    Tester  optimization pass 5c54f4f78b82bace (0, 87) started
IS      0       19:17:58.607    Symbols #Corn_U9: symbol to be synchronized
NI      0       19:17:58.631    Symbols #Corn_U9: symbol synchronized, 3864 bytes of symbol info received
CI      0       19:17:58.662    History #Corn_U9: load 31 bytes of history data to synchronize in 0:00:00.031
KL      0       19:17:58.662    History #Corn_U9: history synchronized from 2018.01.02 to 2019.07.12
MQ      0       19:17:58.662    Ticks   #Corn_U9: ticks synchronization started
QG      0       19:17:58.686    Ticks   #Corn_U9: load 38 bytes of tick data to synchronize in 0:00:00.031
CS      0       19:17:58.686    Ticks   #Corn_U9: history ticks synchronized from 2019.07.11 to 2019.07.12
FL      0       19:17:58.694    History #Corn_U9,M30: history cache allocated for 4373 bars and contains 4301 bars from 2018.01.02 00:00 to 2019.07.11 21:00
DM      0       19:17:58.694    History #Corn_U9,M30: history begins from 2018.01.02 00:00
JH      0       19:17:58.723    Tester  5c54f4f78b82bace (0, 87) : passed in 0:00:00.067
DP      0       19:17:59.610    Tester  optimization pass fbf7ca7bd63934fe (1, 355) started
DD      0       19:17:59.622    Tester  fbf7ca7bd63934fe (1, 355) : passed in 0:00:00.011
DI      0       19:18:00.171    Tester  optimization pass fe37185cca9ce6d4 (2, 435) started
HL      0       19:18:00.183    Tester  fe37185cca9ce6d4 (2, 435) : passed in 0:00:00.011

.....

HG      0       19:19:17.013    Tester  optimization pass b398fcdb3d888321 (31, 366) started
RS      0       19:19:17.024    Tester  b398fcdb3d888321 (31, 366) : passed in 0:00:00.011
ML      0       19:29:12.112    Tester  account info found with currency USD
FD      0       19:29:12.425    Network 1482 bytes of tester parameters loaded
KP      0       19:29:12.425    Network 5820 bytes of input parameters loaded
LE      0       19:29:12.425    Tester  job 6713572051640155864 received from Cloud Server
OM      0       19:29:12.425    Tester  file added, 52170 bytes loaded
NK      0       19:29:12.425    Network 2748 bytes of optimized inputs info loaded
RP      0       19:29:12.425    Tester  successfully initialized
PE      0       19:29:12.425    Network 151 Kb of total initialization data received
MR      0       19:29:12.425    Tester  Intel Core i7-8700T  @ 2.40GHz, 65482 MB
EH      0       19:29:12.425    Tester  forward optimization pass a9e31deab0ff5778 (0, 1891) started
RN      0       19:29:13.366    History #Corn_U9: load 31 bytes of history data to synchronize in 0:00:00.361
NR      0       19:29:13.366    History #Corn_U9: history synchronized from 2018.01.02 to 2019.07.12
FD      0       19:29:13.366    Ticks   #Corn_U9: ticks synchronization started
FR      0       19:29:13.688    Ticks   #Corn_U9: load 38 bytes of tick data to synchronize in 0:00:00.328
II      0       19:29:13.688    Ticks   #Corn_U9: history ticks synchronized from 2019.07.11 to 2019.07.12
QG      0       19:29:13.695    History #Corn_U9,M30: history cache allocated for 4373 bars and contains 4301 bars from 2018.01.02 00:00 to 2019.07.11 21:00
OJ      0       19:29:13.695    History #Corn_U9,M30: history begins from 2018.01.02 00:00
OR      0       19:29:13.723    Tester  a9e31deab0ff5778 (0, 1891) : passed in 0:00:00.044
OR      0       19:29:14.053    Tester  forward optimization pass 1f08fe6122dfc327 (0, 5462) started
NF      0       19:29:14.066    Tester  1f08fe6122dfc327 (0, 5462) : passed in 0:00:00.012
HR      0       19:29:14.187    Tester  forward optimization pass 4ca69bcc18b7bfd6 (0, 5884) started
QG      0       19:29:14.233    Tester  4ca69bcc18b7bfd6 (0, 5884) : passed in 0:00:00.014
LF      0       19:29:14.297    Tester  forward optimization pass 3284a159be77f0f1 (0, 6610) started
OL      0       19:29:14.308    Tester  3284a159be77f0f1 (0, 6610) : passed in 0:00:00.011
HI      0       19:29:14.492    Tester  forward optimization pass 77185483ed9254a2 (0, 1281) started
LH      0       19:29:14.504    Tester  77185483ed9254a2 (0, 1281) : passed in 0:00:00.011
GP      0       19:29:14.676    Tester  forward optimization pass d0d3a5ea6d2461ba (0, 3451) started
JH      0       19:29:14.712    Tester  d0d3a5ea6d2461ba (0, 3451) : passed in 0:00:00.013
OS      0       19:31:27.919    Tester  account info found with currency USD
KH      0       19:31:28.094    Network 1482 bytes of tester parameters loaded
CQ      0       19:31:28.094    Network 5820 bytes of input parameters loaded
QD      0       19:31:28.094    Network 2748 bytes of optimized inputs info loaded
PE      0       19:31:28.094    Tester  successfully initialized
QK      0       19:31:28.094    Network 161 Kb of total initialization data received
KN      0       19:31:28.094    Tester  Intel Core i7-8700T  @ 2.40GHz, 65482 MB
LH      0       19:31:28.094    Tester  forward optimization pass 8c276aceb9bdf42d (0, 2364) started
GG      0       19:31:28.102    History #Corn_U9: symbol tick base found
GP      0       19:31:28.710    History #Corn_U9: load 31 bytes of history data to synchronize in 0:00:00.025
KE      0       19:31:28.710    History #Corn_U9: history synchronized from 2018.01.02 to 2019.07.12
FI      0       19:31:28.710    Ticks   #Corn_U9: ticks synchronization started
KN      0       19:31:28.710    Ticks   #Corn_U9: ticks synchronized already
GG      0       19:31:28.733    Tester  8c276aceb9bdf42d (0, 2364) : passed in 0:00:00.030

Ich denke, da ist aber noch Einiges im cache und die Durchlaufzeiten (0:00:00.030) sind so kurz, dass sie 'unsichtbar bleiben.

 
Christian:

Kann ich nicht, ich denke bei 24,1 gb ist die Grenze intern im Agent für das Temp Verzeichniss

Und was zeigt dann Dein Screenshot an mit 99,6%:


123
Neuer Kommentar
Grund der Beschwerde: