What is JIT conflation (RTO) and Time conflation (RTMDS WebSocket)

MayurC
MayurC LSEG
edited April 24 in TREP Infrastructure

Our client is currently having an app based on Python that consumes RT data. They are currently using RTO which is maximum of 3 updates per second for quotes. Going forward they will use the same application to connect to RTMDS via WebSocket (300ms Conflated Service). Both RTO and RTMDS WebSocket are conflated service.

Query:

  • Is the conflation in RTO and on WebSocket over RTMDS the same.
  • If yes, then fine but if not, then what is the difference and how will it impact client application.
  • Will there be any difference in the way client will receive data in terms qos or, throughput or number of updates or CPU load or network bandwidth.
  • Are there any points to consider in terms of data throughput/difference for client applications that want to move from RTO to RTMDS WebSocket.
  • What is JIT conflation (RTO) and Time conflation (RTMDS WebSocket). Is this something we associate LSEG deliveries with.
Tagged:

Best Answer

  • Jirapongse
    Jirapongse ✭✭✭✭✭
    Answer ✓

    @MayurC

    Thank you for reaching out to us.

    These questions are more related to the settings on RTMDS and behaviors of RTO and RTMDS.

    Please contact the RTMDS and RTO support team directly to answer these questions.

Categories