路透RFA消息队列的消息量很大,导致内存溢出
我是中国进出口银行的路透数据源开发厂商,有个问题我想咨询一下
我使用JAVA RFA,版本付下
Manifest-Version: 1.0
Specification-Title: Classes for RFAJ 5.1
Implementation-Version: Build 2004.12.15
Created-By: 1.4.0_01 (Sun Microsystems Inc.)
Specification-Vendor: Reuters
连接路透数据源服务器,连接配置详见附件subscribe.txt
报文订阅,详见附件code.txt
报文处理,详见附件comsume.txt
在处理一段时间候,出现了如附件outofmemory.jpg的内存溢出问题outofmemofy.jpg
Best Answer
-
The latest release of RFA Java that supports the Market Data programming interface (SSL connection) is RFA Java 7.6.1.L1 release. However this would require the upgrade of Java version as well since RFA Java 7.4 or higher requires Java 7.
From the given heap screen snapshot, large amount of memory was retained by EventQueue object, which basically holds data events received from the infrastructure. This indicates the possibility that a lot of data events were pending (for processing) in the event queue and the application was likely experiencing the slow consumer condition - the application did not process events fast enough.
Generally, there are two main approaches to address the slow consumer problem, i.e. a) improving the event processing capability of the application, and b) reducing the number of updates (by applying update conflation).
To improve the event processing, the developer could review and optimize the event processing routine so that less time is spent on processing events. The application can also be revised to have multiple sessions and connections (having more threads) to distribute the workload across different CPU cores.
On the other hand, if the application cannot be changed, performing the update conflation (on the infrastructure) should be considered. This would reduce the number of updates the application has to handle; however, at the expense of not having all ticks of updates.0
Answers
-
Please see the following answer investigating RFA memory growth. Rising data rates with slow consumers, either by hardware limits or by complex processing will see additional buffer consumption and eventual memory exhaustion.
It is recommended to investigate enabling just-in-time conflation in TREP to reduce the data rates being presented to the consuming application during peak trading hours.
Note that RFA/Java 5.x, 6.x, 7.0, and 7.2 are no longer supported, similarly JRE versions 4, 5, and 6. Code changes will be required to upgrade, and it may be easier to migrate to the new Elektron SDK (EMA) instead.
0
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
- 705 Datastream
- 1.5K DSS
- 633 Eikon COM
- 5.2K Eikon Data APIs
- 14 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 6 Trading API
- 3K Elektron
- 1.5K EMA
- 259 ETA
- 569 WebSocket API
- 40 FX Venues
- 16 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
- 4 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 284 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 24 RDMS
- 2.2K Refinitiv Data Platform
- 879 Refinitiv Data Platform Libraries
- 5 LSEG Due Diligence
- 1 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
- 123 Open DACS
- 1.1K RFA
- 108 UPA
- 196 TREP Infrastructure
- 232 TRKD
- 919 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 103 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛