Idle work
Hello.
I have noticed a strange behaviour of MetaTrader 5 Tester Strategy. At about 8 pm the processor was loaded to its full capacity (8 cores) and was continuously executing something until about 11 pm. At the same time in the tester the test time was completely unchanged. So I was giving away the resources of 8 cores for several hours for free?! Please solve the problem that has arisen.
Yes, there was something like that yesterday. It felt like six cores were flailing around for 10 minutes, but in why went one minute. And it's not the first time this has happened (presumably it coincides with the agents update).
And what makes you think that something was handed out there?
If the processor was loaded 100% in the tester and the logs say the same, what was it? was the tester just dabbling for a few hours? maybe it is calculating the number of pi for itself to an infinite degree? The environment is designed to parallelise the optimisation process across the network, giving you a chance to make a profit on your computer's resources.
Yes, there was something like that yesterday. It felt like six cores were hammering for 10 minutes, and then it went into one minute. And it's not the first time it's happened (presumably it coincides with the agents update).
Your cores were hammering for 10 minutes, mine were hammering for almost three hours!
If the processor was loaded 100% in the tester and the logs say the same, what was it? was the tester just messing around for a few hours? maybe it is calculating the number of pi for itself to an infinite degree? The environment is designed to parallelize the optimization process across the network, giving you a chance to capitalize on your computer's resources.
Check if your account name has been reset (with the sales checkbox checked).
Seems to be related to Windows 10 upgrade to 20H2.
Check to see if the account name has been reset (with sales ticked).
Seems to be related to Windows 10 upgrade to 20H2.
No. Everything is still as it was (account and ticked). Windows is not updating! I have this option disabled.
Check to see if the account name has been reset (with sales ticked).
Seems to be related to Windows 10 upgrade to 20H2.
And it has nothing to do with the update. If you look at the logs, you can see that the tester received a task and started running it! The execution time of this task was about 3 hours for each of the cores!
DP 0 19:50:37.026 Network 4372 bytes of account info loaded DH 0 19:50:37.026 Network 1482 bytes of tester parameters loaded PL 0 19:50:37.026 Network 22716 bytes of input parameters loaded LF 0 19:50:37.141 Network 575079 bytes of symbols list loaded (75753 symbols) JS 0 19:50:37.141 Tester job 6906483157734798975 received from Cloud Server RQ 0 19:50:37.141 Tester file added, 906232 bytes loaded LN 0 19:50:37.141 Network 28668 bytes of optimized inputs info loaded JM 0 19:50:37.142 Tester successfully initialized MP 0 19:50:37.142 Network 2215 Kb of total initialization data received JE 0 19:50:37.142 Tester AMD Ryzen 7 2700 X Eight-Core Processor, 32719 MB NF 0 19:50:37.142 Tester optimization pass 206 started DM 0 19:50:37.156 Symbols WIN$N: symbol to be synchronized LN 0 19:50:37.212 Symbols WIN$N: symbol synchronized, 3720 bytes of symbol info received CS 0 19:51:23.533 History WIN$N: load 25 bytes of history data to synchronize in 0:00:00.152 NF 0 19:51:23.533 History WIN$N: history synchronized from 2019.01.02 to 2020.12.14 RG 0 19:51:23.571 History WIN$N,M1: history cache allocated for 493875 bars and contains 133625 bars from 2019.01.02 09:00 to 2019.12.30 18:09 LJ 0 19:51:23.571 History WIN$N,M1: history begins from 2019.01.02 09:00 FQ 0 19:51:23.614 History WIN$N,Monthly: history cache allocated for 25 bars and contains 12 bars from 2019.01.01 00:00 to 2019.12.01 00:00 OQ 0 19:51:23.614 History WIN$N,Monthly: history begins from 2019.01.01 00:00 KG 0 19:51:23.642 History WIN$N,Weekly: history cache allocated for 104 bars and contains 53 bars from 2018.12.30 00:00 to 2019.12.29 00:00 QL 0 19:51:23.642 History WIN$N,Weekly: history begins from 2018.12.30 00:00 CG 0 19:51:23.671 History WIN$N,Daily: history cache allocated for 498 bars and contains 248 bars from 2019.01.02 00:00 to 2019.12.30 00:00 RK 0 19:51:23.671 History WIN$N,Daily: history begins from 2019.01.02 00:00 KL 0 22:29:53.310 Tester tester agent shutdown started
Six agents idled for about two hours today.
Here's the log of one of the agents: the time 17:06:44.043 is the start time of the tests, when the agent received the tasks, I watched this file in the process - there was the last entry 17:06:44.043. It was only when the agents stopped counting something there (18:53:36.946) that the rest of the entries appeared. I allocated a block, which had been ramming for about two hours, but no payment had gone for it:
ED 0 17:01:57.177 Tester Intel Core i7-9750 H @ 2.60 GHz, 32574 MB MN 0 17:06:44.043 rescan needed IN 0 17:06:45.260 Network connected to agent1.mql5.net FG 0 17:06:46.706 Network connected to agent2.mql5.net QP 0 17:06:48.470 Network connected to agent3.mql5.net FI 0 17:06:49.805 Network connected to agent1.mql5.net NR 0 17:06:51.249 Network connected to agent2.mql5.net CK 0 17:06:53.007 Network connected to agent3.mql5.net MD 0 17:06:54.338 Network connected to agent1.mql5.net LM 0 17:06:55.786 Network connected to agent2.mql5.net JF 0 17:06:57.545 Network connected to agent3.mql5.net JM 0 17:06:58.833 Network MQL5 Cloud Network server agent3.mql5.net selected after rescan (ping 13 ms) QR 0 17:06:58.852 Network connected to agent3.mql5.net JD 0 17:06:58.891 Network authorized on agent3.mql5.net for barabashkakvn LS 0 17:06:59.896 Tester account info found with currency RUR GE 0 17:07:00.903 Network 813 bytes of symbols list loaded (157 symbols) OM 0 17:07:00.903 Tester successfully initialized EK 0 17:07:00.903 Network 2556 bytes of total initialization data received QO 0 17:07:00.903 Tester Intel Core i7-9750 H @ 2.60 GHz, 32574 MB PE 0 17:07:00.903 Tester optimization pass 7367 started IO 0 17:07:00.922 Symbols EURUSD: symbol to be synchronized DI 0 17:07:00.944 Symbols EURUSD: symbol synchronized, 3720 bytes of symbol info received NR 0 17:07:01.471 History EURUSD: load 27 bytes of history data to synchronize in 0:00:00.022 KO 0 17:07:01.471 History EURUSD: history synchronized from 2019.01.02 to 2020.12.18 OI 0 17:07:01.596 History EURUSD,M5: history cache allocated for 146488 bars and contains 130442 bars from 2019.01.02 01:00 to 2020.09.30 23:55 ND 0 17:07:01.596 History EURUSD,M5: history begins from 2019.01.02 01:00 GM 0 17:07:01.974 Symbols EURRUR: symbol to be synchronized DG 0 17:07:01.996 Symbols EURRUR: symbol synchronized, 3720 bytes of symbol info received KJ 0 17:07:02.366 History EURRUR: load 27 bytes of history data to synchronize in 0:00:00.028 EN 0 17:07:02.366 History EURRUR: history synchronized from 2019.01.03 to 2020.12.18 DO 0 17:07:02.367 Symbols USDRUR: symbol to be synchronized PK 0 17:07:02.391 Symbols USDRUR: symbol synchronized, 3720 bytes of symbol info received RL 0 17:07:02.611 History USDRUR: load 27 bytes of history data to synchronize in 0:00:00.020 LP 0 17:07:02.611 History USDRUR: history synchronized from 2019.01.03 to 2020.12.18 DJ 0 18:53:36.946 Tester tester agent shutdown started GR 0 18:53:36.946 Tester shutdown tester machine KK 0 18:53:36.957 Tester tester process stopped ND 0 18:53:36.957 Tester tester agent shutdown finished LO 0 18:53:36.957 rescan needed RI 0 18:53:39.302 Network connected to agent1.mql5.net LP 0 18:53:40.903 Network connected to agent2.mql5.net DO 0 18:53:42.661 Network connected to agent3.mql5.net MF 0 18:53:43.999 Network connected to agent1.mql5.net JM 0 18:53:45.450 Network connected to agent2.mql5.net CD 0 18:53:47.207 Network connected to agent3.mql5.net NS 0 18:53:48.542 Network connected to agent1.mql5.net OJ 0 18:53:49.996 Network connected to agent2.mql5.net DQ 0 18:53:51.751 Network connected to agent3.mql5.net EE 0 18:53:53.042 Network MQL5 Cloud Network server agent3.mql5.net selected after rescan (ping 13 ms) IN 0 18:53:53.065 Network connected to agent3.mql5.net GH 0 18:53:53.117 Network authorized on agent3.mql5.net for barabashkakvn FM 0 18:54:54.562 Network connected to agent3.mql5.net CH 0 18:54:54.612 Network authorized on agent3.mql5.net for barabashkakvn NN 0 18:55:56.055 Network connected to agent3.mql5.net OI 0 18:55:56.099 Network authorized on agent3.mql5.net for barabashkakvn NO 0 18:57:47.864 Startup service shutdown initialized IF 0 18:57:47.864 Exit shutdown thread started JL 0 18:57:47.945 Server MetaTester 5 stopped
Similar logs for all agents.
Then at 18:57:47.864 I stopped all agents.
Six agents idled for about two hours today.
Here's the log of one of the agents: the time 17:06:44.043 is the start time of the tests, when the agent received the tasks, I watched this file in the process - there was the last entry 17:06:44.043. It was only when the agents stopped counting something there (18:53:36.946) that the rest of the entries appeared. I allocated a block, which had been ramming for about two hours, but no payment had gone for it:
Similar logs for all the agents.
Then at 18:57:47.864 I stopped all agents.
Looks like we're getting fucked.
Six agents idled for about two hours today.
Here's the log of one of the agents: the time 17:06:44.043 is the start time of the tests, when the agent received the tasks, I watched this file in the process - there was the last entry 17:06:44.043. It was only when the agents stopped counting something there (18:53:36.946) that the rest of the entries appeared. I allocated a block, which had been ramming for about two hours, but no payment had gone for it:
Similar logs for all the agents.
Then at 18:57:47.864 I stopped all agents.
You have to understand that this is not a way to make money, it's just your desire to do charity for MQ, and the industry in general.
I don't abandon agents, but I have brought the number of agents to a reasonable level.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
Hello.
I have noticed a strange behaviour of MetaTrader 5 Tester Strategy. At about 8 PM the processor was loaded to its full capacity (8 cores) and was continuously executing something until about 11 PM. At the same time in the tester the test time was completely unchanged. So I was giving away the resources of 8 cores for several hours for free?! Please solve the problem that occurred.