Switched to using EmaConfig.xml to handle multiple hosts fallback, but it led to slower processing.

Earlier we used to point to a single host using the config.host() api in the EmaFactory.createOmmConsumer. But recently we planned to use the EmaConfig.xml file to handle auto fallback using multiple hosts. But that has significantly increased our processing time.
We are seeing a lot new xml logs, which weren't there earlier when we weren't using EmaConfig.xml. Our EmaConfig.xml is setup to have a single consumer and it has multiple channels and in the application we are registering the consumer with the consumer we are creating.
Any ideas why it might be so slow?
Best Answer
-
It looks like to be a trace file.
You can disable it.
2
Answers
-
Thank you for reaching out to us.
Please provide more information regarding this issue.
- What version of EMA are you using?
- What do you mean by a lot of new xml logs? Can you share their content?
- Please share the EmaConfig.xml file that you are using.
- How do you determine that the application is slower when using the configuration file?
0 -
- 1. ema version is 3.3.0.1
- 2. xml tags that can be seen are <seriesEntry>, <elementlist>, <arrayentry>, <array> with a lots more data
- 3. EmaConfig.xml file is setup similar to 3.4.9 example from emaj config guide pdf. We just omitted port and channel type, letting it use the default values.
- 4. we are determining slowness in terms of completion time of the process. Where using the same host without the xml config we are done in a minute, whereas with the xml config on average it takes us 4 minutes to complete.
0 -
Yes, it was related to the XmlTraceToStdout. Too much logging to console was slowing down the overall process. Thanks for the help.
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
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 279 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 716 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
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛