2015.09.0106:15:00.037 Trades '1007933': buy limit 1.00 LKOH-9.15 at 23488 placed for execution in7 ms
2015.09.0106:15:00.029 Trades '1007933': buy limit 1.00 LKOH-9.15 at 234882015.09.0106:15:00.027 Trades '1007933': sell limit 1.00 LKOH-9.15 at 26488 placed for execution in212 ms
2015.09.0106:14:59.815 Trades '1007933': sell limit 1.00 LKOH-9.15 at 264882015.09.0106:14:57.782 Trades '1007933': buy limit 1.00 LKOH-9.15 at 24833 placed for execution in18 ms
2015.09.0106:14:57.764 Trades '1007933': buy limit 1.00 LKOH-9.15 at 24833
2015.09.0106:17:49.459 Trades '1007933': cancel order #22085056 buy limit 1.00 LKOH-9.15 at 23488 placed for execution in20 ms
2015.09.0106:17:49.438 Trades '1007933': cancel order #22085056 buy limit 1.00 LKOH-9.15 at 234882015.09.0106:17:49.435 Trades '1007933': cancel order #22085055 sell limit 1.00 LKOH-9.15 at 26488 placed for execution in327 ms
2015.09.0106:17:49.108 Trades '1007933': cancel order #22085055 sell limit 1.00 LKOH-9.15 at 264882015.09.0106:17:47.084 Trades '1007933': cancel order #22085054 buy limit 1.00 LKOH-9.15 at 24900 placed for execution in16 ms
2015.09.0106:17:47.068 Trades '1007933': cancel order #22085054 buy limit 1.00 LKOH-9.15 at 249002015.09.0106:17:45.411 Trades '1007933': buy limit 1.00 LKOH-9.15 at 23488 placed for execution in21 ms
2015.09.0106:17:45.389 Trades '1007933': buy limit 1.00 LKOH-9.15 at 234882015.09.0106:17:45.388 Trades '1007933': sell limit 1.00 LKOH-9.15 at 26488 placed for execution in8 ms
RE 012:03:35.211 Trades '679854': buy limit 1.00 Si-9.15 at 64040 placed for execution in6 ms
PH 012:03:35.416 Trades '679854': cancel order #5378363 sell limit 1.00 Si-9.15 at 70476
LO 012:03:35.723 Trades '679854': cancel order #5378363 sell limit 1.00 Si-9.15 at 70476 placed for execution in307 ms
MR 012:03:35.724 Trades '679854': cancel order #5378364 buy limit 1.00 Si-9.15 at 64040
NJ 012:03:35.731 Trades '679854': cancel order #5378364 buy limit 1.00 Si-9.15 at 64040 placed for execution in6 ms
演示公开赛(甚至没有计算在内)
OF 212:02:26.322 Trades '1007933': failed cancel order #22194460 sell limit 1.00 Si-9.15 at 70476.00000 [Invalid request]
MI 212:02:26.322 Trades '1007933': failed cancel order #22194462 buy limit 1.00 Si-9.15 at 64040.00000 [Invalid request]
HD 012:02:26.526 Trades '1007933': cancel order #22194460 sell limit 1.00 Si-9.15 at 70476
CH 012:02:26.536 Trades '1007933': cancel order #22194460 sell limit 1.00 Si-9.15 at 70476 placed for execution in10 ms
NF 012:02:26.537 Trades '1007933': cancel order #22194462 buy limit 1.00 Si-9.15 at 64040
IR 012:02:26.549 Trades '1007933': cancel order #22194462 buy limit 1.00 Si-9.15 at 64040 placed for execution in12 ms
HQ 0 12:03:07.223 Trades '1007933': cancel order #22195150 sell limit 1.00 Si-9.15 at 70476 placed for execution in 13 ms
LI 0 12:03:07.225 Trades '1007933': cancel order #22195151 buy limit 1.00 Si-9.15 at 64040
LF 0 12:03:07.519 Trades '1007933': cancel order #22195151 buy limit 1.00 Si-9.15 at 64040 placed for execution in 294 ms
NE 0 12:03:07.709 Trades '1007933': sell limit 1.00 Si-9.15 at 70476
FL 0 12:03:07.720 Trades '1007933': sell limit 1.00 Si-9.15 at 70476 placed for execution in 11 ms
LG 0 12:03:07.721 Trades '1007933': buy limit 1.00 Si-9.15 at 64040
KK 0 12:03:07.731 Trades '1007933': buy limit 1.00 Si-9.15 at 64040 placed for execution in 9 ms
EO 012:11:14.206 Trades 'xxxxx': cancel order #1782492 buy limit 1.00 Si-9.15 at 62964
DJ 012:11:14.224 Trades 'xxxxx': cancel order #1782492 buy limit 1.00 Si-9.15 at 62964 placed for execution in19 ms
CG 012:11:16.223 Trades 'xxxxx': sell limit 1.00 Si-9.15 at 69416
CL 012:11:16.365 Trades 'xxxxx': sell limit 1.00 Si-9.15 at 69416 placed for execution in125 ms
IS 012:11:16.419 Trades 'xxxxx': buy limit 1.00 Si-9.15 at 62964
RK 012:11:16.451 Trades 'xxxxx': buy limit 1.00 Si-9.15 at 62964 placed for execution in31 ms
IL 012:11:18.442 Trades 'xxxxx': cancel order #1782495 sell limit 1.00 Si-9.15 at 69416
FR 012:11:18.662 Trades 'xxxxx': cancel order #1782495 sell limit 1.00 Si-9.15 at 69416 placed for execution in220 ms
GI 012:11:18.978 Trades 'xxxxx': cancel order #1782496 buy limit 1.00 Si-9.15 at 62964
NE 012:11:19.009 Trades 'xxxxx': cancel order #1782496 buy limit 1.00 Si-9.15 at 62964 placed for execution in31 ms
JF 012:11:21.004 Trades 'xxxxx': sell limit 1.00 Si-9.15 at 69416
EN 012:11:21.083 Trades 'xxxxx': sell limit 1.00 Si-9.15 at 69416 placed for execution in78 ms
OD 012:11:21.141 Trades 'xxxxx': buy limit 1.00 Si-9.15 at 62964
GO 012:11:21.368 Trades 'xxxxx': buy limit 1.00 Si-9.15 at 62964 placed for execution in226 ms
FR 012:11:23.364 Trades 'xxxxx': cancel order #1782497 sell limit 1.00 Si-9.15 at 69416
NF 012:11:23.444 Trades 'xxxxx': cancel order #1782497 sell limit 1.00 Si-9.15 at 69416 placed for execution in80 ms
MH 012:11:23.646 Trades 'xxxxx': cancel order #1782498 buy limit 1.00 Si-9.15 at 62964
ED 012:11:23.755 Trades 'xxxxx': cancel order #1782498 buy limit 1.00 Si-9.15 at 62964 placed for execution in109 ms
OD 012:11:25.755 Trades 'xxxxx': sell limit 1.00 Si-9.15 at 69416
LM 012:11:25.789 Trades 'xxxxx': sell limit 1.00 Si-9.15 at 69416 placed for execution in32 ms
PF 012:11:25.863 Trades 'xxxxx': buy limit 1.00 Si-9.15 at 62964
IM 012:11:25.893 Trades 'xxxxx': buy limit 1.00 Si-9.15 at 62964 placed for execution in30 ms
FS 012:11:27.926 Trades 'xxxxx': cancel order #1782499 sell limit 1.00 Si-9.15 at 69416
RG 012:11:28.271 Trades 'xxxxx': cancel order #1782499 sell limit 1.00 Si-9.15 at 69416 placed for execution in344 ms
MK 012:11:28.281 Trades 'xxxxx': cancel order #1782500 buy limit 1.00 Si-9.15 at 62964
CF 012:11:28.298 Trades 'xxxxx': cancel order #1782500 buy limit 1.00 Si-9.15 at 62964 placed for execution in18 ms
JS 012:11:30.301 Trades 'xxxxx': sell limit 1.00 Si-9.15 at 69416
PL 012:11:30.332 Trades 'xxxxx': sell limit 1.00 Si-9.15 at 69416 placed for execution in30 ms
LG 012:11:30.337 Trades 'xxxxx': buy limit 1.00 Si-9.15 at 62964
OO 012:11:30.364 Trades 'xxxxx': buy limit 1.00 Si-9.15 at 62964 placed for execution in26 ms
EP 012:11:32.364 Trades 'xxxxx': cancel order #1782502 sell limit 1.00 Si-9.15 at 69416
MF 012:11:32.555 Trades 'xxxxx': cancel order #1782502 sell limit 1.00 Si-9.15 at 69416 placed for execution in191 ms
GE 012:11:32.560 Trades 'xxxxx': cancel order #1782503 buy limit 1.00 Si-9.15 at 62964
NQ 012:11:32.588 Trades 'xxxxx': cancel order #1782503 buy limit 1.00 Si-9.15 at 62964 placed for execution in28 ms
LR 012:11:34.583 Trades 'xxxxx': sell limit 1.00 Si-9.15 at 69416
MI 012:11:34.868 Trades 'xxxxx': sell limit 1.00 Si-9.15 at 69416 placed for execution in284 ms
EH 012:11:34.873 Trades 'xxxxx': buy limit 1.00 Si-9.15 at 62964
KS 012:11:35.176 Trades 'xxxxx': buy limit 1.00 Si-9.15 at 62964 placed for execution in303 ms
FQ 012:11:37.176 Trades 'xxxxx': cancel order #1782505 sell limit 1.00 Si-9.15 at 69416
DJ 012:11:37.208 Trades 'xxxxx': cancel order #1782505 sell limit 1.00 Si-9.15 at 69416 placed for execution in32 ms
GD 012:11:37.214 Trades 'xxxxx': cancel order #1782506 buy limit 1.00 Si-9.15 at 62964
MS 012:11:37.246 Trades 'xxxxx': cancel order #1782506 buy limit 1.00 Si-9.15 at 62964 placed for execution in31 ms
QP 012:11:39.239 Trades 'xxxxx': sell limit 1.00 Si-9.15 at 69416
GI 012:11:39.256 Trades 'xxxxx': sell limit 1.00 Si-9.15 at 69416 placed for execution in17 ms
NJ 012:11:39.262 Trades 'xxxxx': buy limit 1.00 Si-9.15 at 62964
DQ 012:11:39.279 Trades 'xxxxx': buy limit 1.00 Si-9.15 at 62964 placed for execution in16 ms
PG 012:11:41.270 Trades 'xxxxx': cancel order #1782507 sell limit 1.00 Si-9.15 at 69416
KH 012:11:41.296 Trades 'xxxxx': cancel order #1782507 sell limit 1.00 Si-9.15 at 69416 placed for execution in26 ms
IG 012:11:41.301 Trades 'xxxxx': cancel order #1782508 buy limit 1.00 Si-9.15 at 62964
QR 012:11:41.312 Trades 'xxxxx': cancel order #1782508 buy limit 1.00 Si-9.15 at 62964 placed for execution in10 ms
IO 012:11:43.317 Trades 'xxxxx': sell limit 1.00 Si-9.15 at 69416
LD 012:11:43.326 Trades 'xxxxx': sell limit 1.00 Si-9.15 at 69416 placed for execution in8 ms
RK 012:11:43.331 Trades 'xxxxx': buy limit 1.00 Si-9.15 at 62964
IP 012:11:43.338 Trades 'xxxxx': buy limit 1.00 Si-9.15 at 62964 placed for execution in7 ms
HE 012:11:45.333 Trades 'xxxxx': cancel order #1782509 sell limit 1.00 Si-9.15 at 69416
LJ 012:11:45.341 Trades 'xxxxx': cancel order #1782509 sell limit 1.00 Si-9.15 at 69416 placed for execution in8 ms
NQ 012:11:45.347 Trades 'xxxxx': cancel order #1782510 buy limit 1.00 Si-9.15 at 62964
KO 012:11:45.356 Trades 'xxxxx': cancel order #1782510 buy limit 1.00 Si-9.15 at 62964 placed for execution in8 ms
MT5演示开机build 1159 6-15 MSK早上--安静平稳,连眼镜都没动。
这里是BCS演示的日志(也很平静,玻璃没有动)。
现在我们必须等待BCSReal 的日志(感谢上帝有一个人)。
但我有一种预感,我们将不得不写一份关于技术性真实的集体投诉。
迈克尔,我可以通过分析你在Discovery接入点的登录日志告诉你以下情况。
1)当你连接数据中心的日志ping到终端时,这些ping保持在10ms左右,但有尖峰的时候会达到500ms
Access Server2 2015.08.25 08:48:15.666 ***.***.***.*** '*****': login (Client build 1159, cid: *****************************, ping: 10.89 ms)
Access Server3 2015.08.25 00:07:19.069 ***.***.***.*** '*****': login (Client build 1159, cid: *****************************, ping: 500.40 ms)
Access Server3 2015.08.25 08:48:28.696 ***.***.***.*** '*****': login (Client build 1159, cid: *****************************, ping: 12.03 ms)
Access Server3 2015.08.26 04:10:52.879 ***.***.***.*** '*****': login (Client build 1159, cid: *****************************, ping: 506.13 ms)
Access Server3 2015.08.27 01:08:15.820 ***.***.***.*** '*****': login (Client build 1159, cid: *****************************, ping: 8.12 ms)
Access Server2 2015.08.27 01:08:18.776 ***.***.***.*** '*****': login (Client build 1159, cid: *****************************, ping: 7.12 ms)
Access Server2 2015.08.27 02:32:48.278 ***.***.***.*** '*****': login (Client build 1159, cid: *****************************, ping: 7.07 ms)
Access Server2 2015.08.27 09:05:51.324 ***.***.***.*** '*****': login (Client build 1159, cid: *****************************, ping: 11.65 ms)
Access Server3 2015.08.27 09:06:04.272 ***.***.***.*** '*****': login (Client build 1159, cid: *****************************, ping: 11.75 ms)
这是从接入点到终端的PING。
| зона ответственности Биржи || зона ответственности Открытия || интернет || клиент |
[биржа (ФОРТС)] <==> [шлюз Plaza2] <===> [шлюз в MOEX] <=> [MT5 торговый сервер] <=> [Точка доступа] <================> [Терминал]
所以你可以看到在MT5终端-MT5接入点的路径上已经出现了问题,没有达到交易。
2) 我分析了其他客户的ping,有波动 - 但我没有发现任何稳定的模式(例如,在同一时间大量增加的ping)。
该如何处理?
1) 我们在终端添加了ping记录,该功能将在下一个测试版中提供。当它出来时,我将在这里发布。我们还将在未来的平台上建立组件间的定期ping测量,以寻找(可能的)网络问题。
2)我已经要求Discover提供额外的网络信息。让我们看看这是否有助于找到原因。
3) 我建议你尝试通过访问服务器4工作一段时间--它通过与访问点(2,3)不同的供应商连接到互联网,并且在发现网络内部以不同的方式连接到贸易服务器。
迈克尔,我可以通过分析你在Discovery接入点的登录日志告诉你以下情况。
1)当你连接数据中心的日志ping到终端时,这些ping保持在10ms左右,但有尖峰的时候会达到500ms
Access Server2 2015.08.25 08:48:15.666 ***.***.***.*** '*****': login (Client build 1159, cid: *****************************, ping: 10.89 ms)
Access Server3 2015.08.25 00:07:19.069 ***.***.***.*** '*****': login (Client build 1159, cid: *****************************, ping: 500.40 ms)
Access Server3 2015.08.25 08:48:28.696 ***.***.***.*** '*****': login (Client build 1159, cid: *****************************, ping: 12.03 ms)
Access Server3 2015.08.26 04:10:52.879 ***.***.***.*** '*****': login (Client build 1159, cid: *****************************, ping: 506.13 ms)
Access Server3 2015.08.27 01:08:15.820 ***.***.***.*** '*****': login (Client build 1159, cid: *****************************, ping: 8.12 ms)
Access Server2 2015.08.27 01:08:18.776 ***.***.***.*** '*****': login (Client build 1159, cid: *****************************, ping: 7.12 ms)
Access Server2 2015.08.27 02:32:48.278 ***.***.***.*** '*****': login (Client build 1159, cid: *****************************, ping: 7.07 ms)
Access Server2 2015.08.27 09:05:51.324 ***.***.***.*** '*****': login (Client build 1159, cid: *****************************, ping: 11.65 ms)
Access Server3 2015.08.27 09:06:04.272 ***.***.***.*** '*****': login (Client build 1159, cid: *****************************, ping: 11.75 ms)
这是从接入点到终端的PING。
| зона ответственности Биржи || зона ответственности Открытия || интернет || клиент |
[биржа (ФОРТС)] <==> [шлюз Plaza2] <===> [шлюз в MOEX] <=> [MT5 торговый сервер] <=> [Точка доступа] <================> [Терминал]
所以你可以看到在MT5终端-MT5接入点的路径上已经出现了问题,没有达到交易。
2) 我分析了其他客户的ping,有波动 - 但我没有发现任何稳定的模式(例如,在同一时间大量增加的ping)。
该如何处理?
1) 我们在终端添加了ping记录,该功能将在下一个测试版中提供。当它出来时,我将在这里发布。我们还将在未来的平台上建立组件间的定期ping测量,以寻找(可能的)网络问题。
2)我已经要求Discover提供额外的网络信息。让我们看看这是否有助于找到原因。
3) 我建议你尝试通过访问服务器4工作一段时间--它通过与访问点(2,3)不同的供应商连接到互联网,并且在Discover网络内部与贸易服务器的连接方式不同。
下午好!
好的,我将尝试使用访问服务器4(顺便说一下它的IP和端口),但今天或明天我将得到BCS的日志,然后一切都会清楚。
它似乎已经连接,它变得更好了,但是有一个失败(执行在 910 毫秒) :
不,在访问服务器4 上是一样的。
如果你有兴趣,你可以看到BKS和BKS的演示日志,是在BKS_Test.mq5运行时制作的
演示版BKS每2000个交易有1个延迟(但它是!)。
演示公开赛(甚至没有计算在内)
HQ 0 12:03:07.223 Trades '1007933': cancel order #22195150 sell limit 1.00 Si-9.15 at 70476 placed for execution in 13 ms LI 0 12:03:07.225 Trades '1007933': cancel order #22195151 buy limit 1.00 Si-9.15 at 64040 LF 0 12:03:07.519 Trades '1007933': cancel order #22195151 buy limit 1.00 Si-9.15 at 64040 placed for execution in 294 ms NE 0 12:03:07.709 Trades '1007933': sell limit 1.00 Si-9.15 at 70476 FL 0 12:03:07.720 Trades '1007933': sell limit 1.00 Si-9.15 at 70476 placed for execution in 11 ms LG 0 12:03:07.721 Trades '1007933': buy limit 1.00 Si-9.15 at 64040 KK 0 12:03:07.731 Trades '1007933': buy limit 1.00 Si-9.15 at 64040 placed for execution in 9 ms好吧,这里是BCS真实的摘录(感谢Adept)。
我在2014年12月16日开始了这个主题。
现在是2015年9月。
公平地说,应该注意到原始平台概念造成的普遍延误。
很快就得到了修复,但令人无限遗憾的是,开发人员没有认真对待 "浮动单 "的延迟。
这在交易中被证明是致命的(因为它在不同的经纪商的模拟和真实账户上进行了测试。
很明显,延迟发生在MT5的服务器部分)。
非常遗憾的是,对这个错误的检测是由用户完成的,而不是由开发人员完成的。
虽然雷纳特在2014年12月29日保证,工作将继续进行。
"偶尔出现的浮动反应到终端的交付时间还没有得到解决,我们将继续努力。"