what is a mount vs connection vs channel

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
Answers
-
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.
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.
1 -
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.
1
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 167 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 713 Datastream
- 1.5K DSS
- 639 Eikon COM
- 5.3K Eikon Data APIs
- 20 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 12 Trading API
- 3K Elektron
- 1.5K EMA
- 260 ETA
- 574 WebSocket API
- 42 FX Venues
- 16 FX Market Data
- 2 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 26 Messenger Bot
- 5 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 285 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 25 RDMS
- 2.3K Refinitiv Data Platform
- 20 CFS Bulk File/TM3
- 939 Refinitiv Data Platform Libraries
- 6 LSEG Due Diligence
- 1 LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 12 World-Check Customer Risk Screener
- World-Check On Demand
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 46 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 126 Open DACS
- 1.1K RFA
- 108 UPA
- 197 TREP Infrastructure
- 232 TRKD
- 925 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 107 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛