Websocket order.place method

[vdmdotcom]

Hi, I'm looking for a way to send a new order via the Websocket API.
This has been available for quite some time now, using the order.place method.
(https://developers.binance.com/docs/derivatives/usds-margined-futures/trade/websocket-api#method)
Now I have a problem:
I send an order (for example) at 21:00.00
But at 21:02:15, I receive the ORDER_TRADE_UPDATE :: MARKET NEW event via WSS.
I get an unacceptable delay between the actual order submission via the REST API and the message in WSS.
This problem comes and goes away on its own.
My server is located close to Binance and has no ping or time sync issues.
I hope the WSS order.place method will speed things up.
I'd appreciate any help with code examples or just your clever ideas.

[zhouaini528]

I suspect there are two possibilities: one is message loss, and the other is that you are reading messages too slowly. When you have a large number of order messages, there is a certain probability of loss. You can set queue_count=999 to increase the buffer space and quickly get the latest messages using while(1)$binance->getSubscribes().

If you still can't find the reason, you should set breakpoints in the source code and test to see if you can print out the results you want.

[zhouaini528]

$data=json_decode($data,true);

binance-php/src/Api/WebSocket/SocketServer.php

Line 103 in 11f6f35

$data=json_decode($data,true);

Set a breakpoint here and print $data to see if the order status change can be received in time.

[vdmdotcom]

I interact with binance wss via AsyncTcpConnection

$binance_wss = new AsyncTcpConnection($ws_url.$listenKey, [ 'socket' => [ 'bindto' => $binance_ip.':0' ] ]);
$binance_wss->transport = 'ssl';
$binance_wss->websocketPingInterval = 10;
$binance_wss->onMessage = function ... // handle messages... 

and no any idea where change queue_count (

[zhouaini528]

Did you build your own websocket client? If so, you need to handle it yourself, and there is no queue_count.