irregular ping time?

[tesla1060]

Hi,
I have run the following cmd,

ws connect --ping_interval 5 wss://real.okex.com:8443/ws/v3

but seems I am not getting pong back at around 5sec interval, the interval seems to be ranging from 7-10 sec.
But because I am running command on the same network as the websocket server, the pong should come back a few milliseconds after ping. May I know what is causing the delay, if ping is in fact sending at 5 sec interval

[2020-07-29 18:23:18.459] [info] Uri: /ws/v3
[2020-07-29 18:23:18.459] [info] Headers:
[2020-07-29 18:23:18.459] [info] Connection: upgrade
[2020-07-29 18:23:18.459] [info] Date: Wed, 29 Jul 2020 10:23:18 GMT
[2020-07-29 18:23:18.459] [info] sec-websocket-accept: /5H74Da1za0gSx4Q+z5lubqmkQ4=
[2020-07-29 18:23:18.459] [info] sec-websocket-extensions:
[2020-07-29 18:23:18.459] [info] Server: nginx
[2020-07-29 18:23:18.459] [info] upgrade: websocket
[2020-07-29 18:23:18.460] [info] Received pong
[2020-07-29 18:23:26.678] [info] Received pong
[2020-07-29 18:23:34.899] [info] Received pong
[2020-07-29 18:23:43.119] [info] Received pong
[2020-07-29 18:23:51.456] [info] Received pong
[2020-07-29 18:23:59.697] [info] Received pong
[2020-07-29 18:24:07.914] [info] Received pong
[2020-07-29 18:24:16.134] [info] Received pong
[2020-07-29 18:24:24.354] [info] Received pong
[2020-07-29 18:24:32.822] [info] Received pong
[2020-07-29 18:24:41.040] [info] Received pong
[2020-07-29 18:24:49.262] [info] Received pong
[2020-07-29 18:24:57.598] [info] Received pong
[2020-07-29 18:25:05.935] [info] Received pong
[2020-07-29 18:25:14.156] [info] Received pong
[2020-07-29 18:25:22.373] [info] Received pong
[2020-07-29 18:25:30.594] [info] Received pong

[bsergean]

Unfortunately this is a known issue, I haven't had a chance to debug it yet.

…

On Jul 29, 2020, at 3:32 AM, tesla1060 ***@***.***> wrote: Hi, I have run the following cmd, ws connect --ping_interval 5 wss://real.okex.com:8443/ws/v3 but seems I am not getting pong back at around 5sec interval, the interval seems to be ranging from 7-10 sec. But because I am running command on the same network as the websocket server, the pong should come back a few milliseconds after ping. May I know what is causing the delay, if ping is in fact sending at 5 sec interval [2020-07-29 18:23:18.459] [info] Uri: /ws/v3 [2020-07-29 18:23:18.459] [info] Headers: [2020-07-29 18:23:18.459] [info] Connection: upgrade [2020-07-29 18:23:18.459] [info] Date: Wed, 29 Jul 2020 10:23:18 GMT [2020-07-29 18:23:18.459] [info] sec-websocket-accept: /5H74Da1za0gSx4Q+z5lubqmkQ4= [2020-07-29 18:23:18.459] [info] sec-websocket-extensions: [2020-07-29 18:23:18.459] [info] Server: nginx [2020-07-29 18:23:18.459] [info] upgrade: websocket [2020-07-29 18:23:18.460] [info] Received pong [2020-07-29 18:23:26.678] [info] Received pong [2020-07-29 18:23:34.899] [info] Received pong [2020-07-29 18:23:43.119] [info] Received pong [2020-07-29 18:23:51.456] [info] Received pong [2020-07-29 18:23:59.697] [info] Received pong [2020-07-29 18:24:07.914] [info] Received pong [2020-07-29 18:24:16.134] [info] Received pong [2020-07-29 18:24:24.354] [info] Received pong [2020-07-29 18:24:32.822] [info] Received pong [2020-07-29 18:24:41.040] [info] Received pong [2020-07-29 18:24:49.262] [info] Received pong [2020-07-29 18:24:57.598] [info] Received pong [2020-07-29 18:25:05.935] [info] Received pong [2020-07-29 18:25:14.156] [info] Received pong [2020-07-29 18:25:22.373] [info] Received pong [2020-07-29 18:25:30.594] [info] Received pong — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#232>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC2O6UNCFGRBKADMIEVP2KDR573CXANCNFSM4PLOM6YQ>.

[bsergean]

I think I fixed it, there was a simple time computation bug. Please tell me if it works for you now. (venv) IXWebSocket$ ws connect --ping_interval 5 wss://real.okex.com:8443/ws/v3 Type Ctrl-D to exit prompt... Connecting to url: wss://real.okex.com:8443/ws/v3

ws_connect: connected

[2020-07-29 11:28:05.652] [info] Uri: /ws/v3 [2020-07-29 11:28:05.653] [info] Headers: [2020-07-29 11:28:05.653] [info] CF-Cache-Status: DYNAMIC [2020-07-29 11:28:05.653] [info] CF-RAY: 5ba8e5cb0edbecaf-DFW [2020-07-29 11:28:05.653] [info] cf-request-id: 043d6df2e60000ecafd3036200000001 [2020-07-29 11:28:05.653] [info] Connection: upgrade [2020-07-29 11:28:05.653] [info] Date: Wed, 29 Jul 2020 18:28:05 GMT [2020-07-29 11:28:05.653] [info] Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct" [2020-07-29 11:28:05.653] [info] sec-websocket-accept: Tthd4XAoRC3X25Mxd2ZCkI4mmgA= [2020-07-29 11:28:05.653] [info] sec-websocket-extensions: [2020-07-29 11:28:05.653] [info] Server: cloudflare [2020-07-29 11:28:05.653] [info] Set-Cookie: __cfduid=de5f2bc17a1f3dbab1bbf30e850872aee1596047284; expires=Fri, 28-Aug-20 18:28:04 GMT; path=/; domain=.okex.com; HttpOnly; SameSite=Lax [2020-07-29 11:28:05.653] [info] upgrade: websocket [2020-07-29 11:28:05.928] [info] Received pong ixwebsocket::heartbeat::5s::0 [2020-07-29 11:28:11.107] [info] Received pong ixwebsocket::heartbeat::5s::1 [2020-07-29 11:28:15.930] [info] Received pong ixwebsocket::heartbeat::5s::2 [2020-07-29 11:28:20.939] [info] Received pong ixwebsocket::heartbeat::5s::3 [2020-07-29 11:28:25.954] [info] Received pong ixwebsocket::heartbeat::5s::4 [2020-07-29 11:28:30.952] [info] Received pong ixwebsocket::heartbeat::5s::5 [2020-07-29 11:28:35.941] [info] Received pong ixwebsocket::heartbeat::5s::6 [2020-07-29 11:28:40.963] [info] Received pong ixwebsocket::heartbeat::5s::7 [2020-07-29 11:28:45.951] [info] Received pong ixwebsocket::heartbeat::5s::8 [2020-07-29 11:28:50.945] [info] Received pong ixwebsocket::heartbeat::5s::9 [2020-07-29 11:28:55.945] [info] Received pong ixwebsocket::heartbeat::5s::10 [2020-07-29 11:29:00.955] [info] Received pong ixwebsocket::heartbeat::5s::11 [2020-07-29 11:29:05.964] [info] Received pong ixwebsocket::heartbeat::5s::12 [2020-07-29 11:29:10.973] [info] Received pong ixwebsocket::heartbeat::5s::13 [2020-07-29 11:29:15.968] [info] Received pong ixwebsocket::heartbeat::5s::14 [2020-07-29 11:29:20.961] [info] Received pong ixwebsocket::heartbeat::5s::15 [2020-07-29 11:29:25.973] [info] Received pong ixwebsocket::heartbeat::5s::16 [2020-07-29 11:29:31.149] [info] Received pong ixwebsocket::heartbeat::5s::17 [2020-07-29 11:29:35.976] [info] Received pong ixwebsocket::heartbeat::5s::18 [2020-07-29 11:29:41.029] [info] Received pong ixwebsocket::heartbeat::5s::19 [2020-07-29 11:29:45.977] [info] Received pong ixwebsocket::heartbeat::5s::20 [2020-07-29 11:29:50.977] [info] Received pong ixwebsocket::heartbeat::5s::21 [2020-07-29 11:29:55.983] [info] Received pong ixwebsocket::heartbeat::5s::22

…

On Jul 29, 2020, at 3:32 AM, tesla1060 ***@***.***> wrote: Hi, I have run the following cmd, ws connect --ping_interval 5 wss://real.okex.com:8443/ws/v3 but seems I am not getting pong back at around 5sec interval, the interval seems to be ranging from 7-10 sec. But because I am running command on the same network as the websocket server, the pong should come back a few milliseconds after ping. May I know what is causing the delay, if ping is in fact sending at 5 sec interval [2020-07-29 18:23:18.459] [info] Uri: /ws/v3 [2020-07-29 18:23:18.459] [info] Headers: [2020-07-29 18:23:18.459] [info] Connection: upgrade [2020-07-29 18:23:18.459] [info] Date: Wed, 29 Jul 2020 10:23:18 GMT [2020-07-29 18:23:18.459] [info] sec-websocket-accept: /5H74Da1za0gSx4Q+z5lubqmkQ4= [2020-07-29 18:23:18.459] [info] sec-websocket-extensions: [2020-07-29 18:23:18.459] [info] Server: nginx [2020-07-29 18:23:18.459] [info] upgrade: websocket [2020-07-29 18:23:18.460] [info] Received pong [2020-07-29 18:23:26.678] [info] Received pong [2020-07-29 18:23:34.899] [info] Received pong [2020-07-29 18:23:43.119] [info] Received pong [2020-07-29 18:23:51.456] [info] Received pong [2020-07-29 18:23:59.697] [info] Received pong [2020-07-29 18:24:07.914] [info] Received pong [2020-07-29 18:24:16.134] [info] Received pong [2020-07-29 18:24:24.354] [info] Received pong [2020-07-29 18:24:32.822] [info] Received pong [2020-07-29 18:24:41.040] [info] Received pong [2020-07-29 18:24:49.262] [info] Received pong [2020-07-29 18:24:57.598] [info] Received pong [2020-07-29 18:25:05.935] [info] Received pong [2020-07-29 18:25:14.156] [info] Received pong [2020-07-29 18:25:22.373] [info] Received pong [2020-07-29 18:25:30.594] [info] Received pong — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#232>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC2O6UNCFGRBKADMIEVP2KDR573CXANCNFSM4PLOM6YQ>.

[tesla1060]

yeah! it is working fine now. Thanks for the prompt reply.
I think this lib is really good. I have tried beast before, but it quite difficult to get it right without digging into all the details on networking, your lib has really make life easier.

[bsergean]

Thanks for the good words ! Each library is focused on something, I think that beast is great for performance but this seems to have a 'simplicity' cost.

…

On Jul 29, 2020, at 7:23 PM, tesla1060 ***@***.***> wrote: yeah! it is working fine now. Thanks for the prompt reply. I think this lib is really good. I have tried beast before, but it quite difficult to get it right without digging into all the details on networking, your lib has really make life easier. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#232 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC2O6UPJQT3RZMQ6JBS57KDR6DKRBANCNFSM4PLOM6YQ>.