Better now?
-
-
Replying to @paoloardoino @bitfinex
Not the best latency :(pic.twitter.com/j5nb2mcB5g
1 reply 0 retweets 0 likes -
There are few things that we're working on for that. I'll have an update tomorrow for you. How about cancel latency via ws?
1 reply 0 retweets 0 likes -
Replying to @paoloardoino @bitfinex
Seems its also affected by current issues. And orders doesnt cancel sometimes. I mean my bot cancels it but cancelled order still persists and then removed by cancel all function. Not good.
1 reply 0 retweets 0 likes -
Is this happening cancelling via WS? Interesting I'll investigate / debug that. Are you using simple "oc" or "ox_multi" ? Thanks a lot for your help
1 reply 0 retweets 0 likes -
Replying to @paoloardoino @bitfinex
Im using both it depends on some market conditions. The worst thing is that after immidiate cancelling i need to check whether order was really cancelled or not bc if i will wait too long ill miss good moment. Thats very bad for HFT.
2 replies 0 retweets 0 likes -
Just pushed a patch for `oc` message (`ox_multi` requires more work). That should fix the edge case of having to resubmit cancel. Let me know if it helps
1 reply 0 retweets 0 likes -
Replying to @paoloardoino @bitfinex
I've noticed some order freezing when sending update order request. Could it be affected by patch? And is it possible for order to be suddenly cancelled when sending update request?
1 reply 0 retweets 0 likes -
What do you mean with freezing? The patch just affected 'oc' message. You if you update and cancel them after 1ms it should work normally. Thanks again for the help
1 reply 0 retweets 1 like -
Replying to @paoloardoino @bitfinex
It looks good so far. But latency still not stable. It jumps from 70ms to 300ms.
1 reply 0 retweets 0 likes
Ok, let me try to kick our server side handlers a bit more
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.