lank: Всем привет! Хотелось бы чтобы тем кто предоставляет процессорные мощности платили бы побольше, ну или там бонусы всякие добавляли за каждые 100, 200 тыс. проходов.
EK 009:17:18.532 Network connected to 3.agents.mql5.com
LL 009:17:18.532 Network authorized on 3.agents.mql5.com
PE 009:17:21.480 Network 71876 bytes of input parameters loaded
JQ 009:17:21.480 Tester job 5997523921618883201 received from Cloud Server
CH 009:17:21.480 Tester file added, 112793 bytes loaded
RQ 009:17:21.480 Network 94144 bytes of optimized inputs info loaded
RI 009:17:21.480 Tester successfully initialized
EQ 009:17:21.480 Network 271 Kb of total initialization data received
OF 009:17:21.480 Tester Intel Xeon X5550 @ 2.67 GHz, 12277 MB
GR 009:17:21.480 Tester optimization pass 11713 started
RD 009:17:21.480 History AUDUSD: symbol tick base found
OP 009:27:51.539 Tester cancel expert execution
RD 009:38:52.647 Tester tester agent shutdown
PI 009:43:53.809 Network connected to 3.agents.mql5.com
FQ 009:43:54.030 Network authorized on 3.agents.mql5.com
II 217:18:43.829192.168.22.23 cannot accept connect, agent is busy
PQ 217:19:43.498192.168.22.23 cannot accept connect, agent is busy
QJ 217:19:54.510192.168.22.23 cannot accept connect, agent is busy
HS 217:20:54.485192.168.22.23 cannot accept connect, agent is busy
LL 217:21:54.473192.168.22.23 cannot accept connect, agent is busy
FD 217:23:21.978192.168.22.23 cannot accept connect, agent is busy
FM 217:24:21.454192.168.22.23 cannot accept connect, agent is busy
DF 217:25:36.936192.168.22.23 cannot accept connect, agent is busy
KO 217:26:36.417192.168.22.23 cannot accept connect, agent is busy
GG 217:27:48.318192.168.22.23 cannot accept connect, agent is busy
EP 217:28:48.403192.168.22.23 cannot accept connect, agent is busy
PI 217:29:48.401192.168.22.23 cannot accept connect, agent is busy
RR 217:31:01.722192.168.22.23 cannot accept connect, agent is busy
CJ 217:32:01.403192.168.22.23 cannot accept connect, agent is busy
FS 217:33:01.414192.168.22.23 cannot accept connect, agent is busy
HL 217:34:08.137192.168.22.23 cannot accept connect, agent is busy
ME 217:35:07.404192.168.22.23 cannot accept connect, agent is busy
DM 217:36:07.433192.168.22.23 cannot accept connect, agent is busy
LF 217:37:17.679192.168.22.23 cannot accept connect, agent is busy
JN 017:51:38.248 Startup access rights to common directory successfully checked
OK 017:51:38.248 Startup Service start initialized
QL 017:51:38.248 Startup Create startup thread
RD 017:51:38.248 Startup Thread successfully created
KP 017:51:38.248 Startup MetaTester 5 x64 build 910 (07 Mar 2014)
DD 017:51:38.248 Server MetaTester 5 started on 0.0.0.0:2000
EO 017:51:38.248 Agent OpenCL is not supported
IO 017:51:38.248 Startup initialization finished
大家好！我希望那些提供处理器容量的用户能够支付更多的费用，或者每 10 万、20 万通行证就有奖金。我还想呼吁开发人员，也许他们会读到这篇文章，在用户统计中加入当天执行的通行证数量，现在只显示所有代理的总数
我在计算机上安装了代理后，等待了大约两个月，直到它们开始工作，我把它们放好并忘记，然后打开 pom opa，平均每天工作 4-5 个小时。
是的，计算机工作的价格应该能带来一些东西，当然也应该能证明电费的合理性。如果云计算顾问支持第三方 dlls（带策略），这将是一项更有趣的服务。
以下是我感兴趣的内容。我有一台负载不高的服务器。我在那里放置了 8 个测试代理，并将它们发布到云端。有时我自己也会使用它们。那是很久以前的事了，一切都很正常，没有任何问题。今天我决定运行优化程序，终端显示 8 个远程代理中有 7 个在忙。好吧，我想他们正在云计算....。一个小时过去了，两个小时过去了，他们还是很忙。我决定去仔细看看他们。我进入远程桌面，在资源监控器中看到只有 1 个（我使用的那个）在工作，CPU 有负载，一些内存被占用。总之，它在工作。其他 7 个什么也没做。
注意问题：为什么会这样？
更新：我杀死了空闲进程，它们又自动启动，可供我测试。不过行为很奇怪。
请查看空闲代理的日志记录。这些代理是什么型号？
请将其中一个代理的每日日志文件附在压缩包中。
请查看空闲代理的日志记录。这些代理是什么型号？
请将其中一个代理的每日日志文件附在压缩包中。
这是日志的一部分。我想你不需要更多了。
这是 claude 最后执行的任务，取消时提到了代理繁忙、重启、版本。看来一切正常。