what is a mount vs connection vs channel

erol.komac
erol.komac LSEG
edited August 25 in ETA

Hi team,

Can you please provide some clarifications to the below question. Next to performance this also relates to limiting exchange fees by requiring simultanous access.

When Devs See/Create in ETA

The OS network layer sees

The OS processors see

From a MD Administration point of view, it can be seen as

RsslChannel

netstat --inet -nep sees one TCP/IP socket.

The application’s main thread and one internal dispatch thread (?).

From a DACS mount point of view: It is one DACS mount IF this is the first connection with that login from that box to that particular Reuters destination IP.  Else, this connection is included with the earlier connection.

‘n’ RsslChannels, with the same login and the same Reuters destination IP address

netstat --net -nep sees ‘n’  TCP/IP sockets.

The application’s main thread and ‘n’ additional dispatch threads (?).

From a DACS mount point of view: This is still (at most) one DACS mount because it’s the same login and Reuters destination IP address.

Regards,

Erol

Tagged:

Answers

  • Jirapongse
    Jirapongse ✭✭✭✭✭

    @erol.komac

    Thank you for reaching out to us.

    As far as I know, they are same. The API uses a channel to refer to a connection, whereas the server can refer to a connection as a mount. Regarding DACS mounts, please contact the DACS team directly.

    I assume that the client is using the ETA Reactor in the Value-Added package.

    Each instance of the ETA Reactor leverages multiple threads to help manage inbound and outbound data efficiently. The following figure illustrates a high-level view of the reactor threading model.

    image.png

    For more information, pleaser refer to the chapter 6 Reactor Detailed View in the ETA Value Added Component guide.

    If the client isn't using the ETA Reactor, please specify which API the client is using.

  • Jirapongse
    Jirapongse ✭✭✭✭✭

    You can refer to the following article that summarizes the Real-Time SDK performance test results of consumer, interactive provider, and non-interactive provider applications by focusing on throughput, steady state latency, and average CPU usages over different network protocols such as TCP Socket encrypted and non-encrypted.

    https://developers.lseg.com/en/article-catalog/article/refinitiv-real-time-sdks-performance-test-summary

Categories