Max dacs.snkd client connection - dacs.snkd DACS_MAX_SNKD_CLIENTS=8

Hi we are planning to use the OpenDACS API on a UI connecting back to pair of dacs.snkd or multiple pairs (for multiconnect). The default number of connections on a dacs.snkd it 8 -
# Define the number of Sink Clients that can attach to the dacs.snkd
DACS_MAX_SNKD_CLIENTS=8; export DACS_MAX_SNKD_CLIENTS
We will need to increase this number significantly to achieve our goal - possibly to 300 or 400. According to the DACS manuals the only limitation to setting this parameter is the machine resources but no indication of loading is detailed. In practice can you let me know how much memory each connection to the dacs.snkd uses & is 300 connections realistically possible?
# Define the number of Sink Clients that can attach to the dacs.snkd
DACS_MAX_SNKD_CLIENTS=300; export DACS_MAX_SNKD_CLIENTS
many thanks
Adam
Best Answer
-
Hi Adam,
I've set the max clients higher than your requirement without issue for many years.
it's a good idea to also set the following parameters in the dacs.env for usage capture when using a remote dacs call.
DACS_SNKD_P2P_USAGE
DACS_SNKD_P2P_USAGE_SIZE
I would recommend you get your network team to put a GTM style load balancer address in front of the dacs_snkd's so you at least have a failover in the event of a single dacs_snkd failing and useful to distribute the load across a few dacs_snkd's.
I've used a high client number for many years starting back in the days of Kobra/SASS3 RV mode running over SASS3 and where we did not want local dacs_snkd's on every client PC and used a farm of dacs_snkd's sitting on servers.
Regards Paul
0
Answers
-
Hello @adam.martin,
Refinitiv developers forums are dedicated to general questions and discussions centered around Refinitiv API usage. The majority of forum's members are Refinitiv API developers, moderators are Refinitiv API experts. These are the questions that this forum is most helpful with.
In my view (developer), as a single dacs.snkd is required to be fast, it has gone through release and testing under max of 8 connections, I would not be comfortable increasing max connections to a number far beyond the recommended. As my understanding is, that you are designing for production use, to me, memory requirement would not be the only concern, a full system test under this configuration setting would be required to have reasonable confidence.
If the targeted daemons run on DACS, is remote to the client app, your market data team/admin, who manage your DACS, and the daemon, would be the ultimate decision maker on any config changes, so they would be the first to consult, and if the are a "no", it's a "no-go". If it's your local daemons, you can likely increase the parameter yourself, but then the responsibility for doing so, and the implied system testing would be on you.
You may, as a customer, raise a case with Refinitiv DACS support, via Refinitiv Helpdesk Online perhaps DACS support engineers have more in-depth guidance to share on this matter.
Would it make sense to discuss your use case, why 300-400 connections per daemon are required, perhaps we can be of help in that?
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 687 Datastream
- 1.4K DSS
- 621 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 4 Trading API
- 2.9K Elektron
- 1.4K EMA
- 254 ETA
- 557 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 276 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 669 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 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
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 229 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛