It looks like you're new here. If you want to get involved, click one of these buttons!
The delay could be due to any of the following:
2024-04-15 09:15:00.006 (Thread-11 (run)): Tick data subscription: [1793, 3329, 758529, 2953217, 784129, 60417, 579329, 103425, 197633, 119553, 356865, 4561409, 617473, 975873]
2024-04-15 09:15:00.017 (Thread-11 (run)): ==> Successful
2024-04-15 09:15:00.410 (TickProc ): SAIL:last_price: 2024-04-15 09:12:37 152.9
I've registered both on_ticks and on_message callbacks. For ticks, both the callbacks are getting called - on_ticks with parsed binary data and on_message with message type 2 (for binary) and binary payload, which is what I see from the code. I choose to ignore binary payloads since I don't want to parse them myself.
Like I mentioned in my last post, I'm seeing empty binary payloads right after subscription and before the first tick. If the 500 - 1000 millisecond delay/latency is expected from the client library, I can modify my code to work with this. I'm just trying to understand what's going on.