你好。
我注意到MetaTrader 5测试策略的一个奇怪行为。在晚上8点左右,处理器被加载到其全部容量(8个核心),并持续执行一些东西,直到晚上11点左右。同时,在测试器中,测试时间完全没有变化。所以我是在免费赠送8个核心的资源几个小时?请解决所出现的问题。
是的,昨天就有这样的事情。感觉就像6个核心在甩动10分钟,但在为什么去了1分钟。而且这不是第一次发生这种情况(估计是与代理商的更新相吻合)。
你怎么会认为有东西被递出去了呢?
如果处理器在测试器中被100%加载,而日志中说的也是这样,那是什么原因呢?测试器只是胡闹了几个小时吗?也许它正在为自己计算π的数量,达到了无限的程度?该环境旨在使整个网络的优化过程平行化,让你有机会在计算机资源上获利。
是的,昨天就有这样的事情。感觉就像六个核心在敲打10分钟,然后一分钟就变成了为什么。而且这也不是第一次发生了(估计是与代理商的更新相吻合)。
你的铁芯敲击了10分钟,我的铁芯敲击了近3个小时!你的铁芯敲击了10分钟。
如果处理器在测试器中被100%加载,而日志中说的也是这样,那是什么原因呢?测试器只是胡闹了几个小时吗?也许它正在为自己计算π的数量,达到了无限的程度?该环境旨在将优化过程在整个网络中并行化,使你有机会利用你的计算机资源。
检查您的账户名称是否已被重置(勾选销售复选框)。
似乎与Windows 10升级到20H2有关。
检查账户名称是否已被重置(勾选销售)。
似乎与Windows 10升级到20H2有关。
不,一切都保持原样(账户和勾选)。Windows没有更新!我禁用了这个选项。
检查账户名称是否已被重置(勾选销售)。
似乎与Windows 10升级到20H2有关。
而且这与更新没有关系。如果你看一下日志,你可以看到,测试者收到了一个任务,并开始运行它!这是一个很好的例子。这项任务的执行时间对每个核心来说大约是3个小时!
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
六名特工今天闲置了大约两个小时。
这是其中一个代理的日志:时间17:06:44.043是测试的开始时间,当代理收到任务时,我在过程中观察了这个文件--有最后一条17:06:44.043。只有当特工在那里停止计数的时候(18:53:36.946),其余的条目才出现。我分配了一个区块,它已经冲撞了大约两个小时,但没有人去买它。
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
所有代理人都有类似的日志。
然后在18:57:47.864我停止了所有代理。
六名特工今天闲置了大约两个小时。
这是其中一个代理的日志:时间17:06:44.043是测试的开始时间,当代理收到任务时,我在过程中观察了这个文件--有最后一条17:06:44.043。只有当特工在那里停止计数的时候(18:53:36.946),其余的条目才出现。我分配了一个区块,它已经冲撞了大约两个小时,但没有人去买它。
所有代理人都有类似的日志。
然后在18:57:47.864我停止了所有代理。
看来我们要被耍了。
六名特工今天闲置了大约两个小时。
这是其中一个代理的日志:时间17:06:44.043是测试的开始时间,当代理收到任务时,我在过程中观察了这个文件--有最后一条17:06:44.043。只有当特工在那里停止计数的时候(18:53:36.946),其余的条目才出现。我分配了一个区块,它已经冲撞了大约两个小时,但没有人去买它。
所有代理人都有类似的日志。
然后在18:57:47.864我停止了所有代理。
你要明白,这不是赚钱的方法,只是你想为MQ,以及整个行业做慈善的愿望。
我不放弃代理人,但我已经把代理人的数量带到了一个合理的水平。
你好。
我注意到MetaTrader 5测试策略的一个奇怪行为。在晚上8点左右,处理器被加载到其全部容量(8个核心),并持续执行一些东西,直到晚上11点左右。同时,在测试器中,测试时间完全没有变化。所以我是在免费赠送8个核心的资源几个小时?请解决所发生的问题。