Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • Elektron /
  • ETA /
avatar image
Question by didier.nadeau · Nov 06, 2018 at 04:12 PM · elektronrefinitiv-realtimeelektron-sdkrrteta-apielektron-transport-apiconsumerperformancemonitoring

How to monitor ETA consumer performance

Hi,

When the ETA client does not consume data quickly enough and the output buffer fills up, the provider (ADS) simply disconnect the client without warning.

Is there a way for the consumer to verify if it's consuming data quickly enough ? For instance, is it possible to check the usage of the input buffer ?

Thank you

People who like this

0 Show 0
Comment
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Reply

  • Sort: 
avatar image
REFINITIV
Best Answer
Answer by Jirapongse · Nov 07, 2018 at 05:25 AM

@didier.nadeau

The numInputBuffers cannot be used to verify the slow consumer issue. It is the number of sequential input buffers used by each RsslChannel for data reading. This controls the maximum number of bytes that can be handled with a single network read operation on each channel.

To verify the slow consumer issue on the consumer side, you can use the time difference (in seconds or milliseconds) between the timestamp of the machine and the time field (TRDTIM_1, QUOTIM, TRDTIM_MS, QUOTIM_MS, or SALTIM_MS) in the payload when decoding the data.

If the time difference is rather constant, the application is not a slow consumer. However, if the time difference is exceptionally increased, it is possible that the application is a slow consumer.

You can also re-design the application by separating threads which read and process (decode) the data. For example, the application can have a thread that reads, copies and puts the copied buffer into a queue. Then, it has another thread which gets the copied buffer from the queue and decodes it. With this method, the application can verify the slow consumer issue by verifying the number of copied buffers in the queue.

Comment
zoya faberov

People who like this

1 Show 0 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Watch this question

Add to watch list
Add to your watch list to receive emailed updates for this question. Too many emails? Change your settings >
9 People are following this question.

Related Questions

ERT in Cloud: failed to send AuthToken request

Migrating from NFD to Elektron Transport API MRN - No news received

ETA Partial Updates on Quotes

How to know when BDS (SymbolLists) are available after Elektron Server reboot

Is there anyway to specify what to return for the price tick?

  • Copyright
  • Cookie Policy
  • Privacy Statement
  • Terms of Use
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Alpha
  • App Studio
  • Block Chain
  • Bot Platform
  • Connected Risk APIs
  • DSS
  • Data Fusion
  • Data Model Discovery
  • Datastream
  • Eikon COM
  • Eikon Data APIs
  • Electronic Trading
    • Generic FIX
    • Local Bank Node API
    • Trading API
  • Elektron
    • EMA
    • ETA
    • WebSocket API
  • Intelligent Tagging
  • Legal One
  • Messenger Bot
  • Messenger Side by Side
  • ONESOURCE
    • Indirect Tax
  • Open Calais
  • Open PermID
    • Entity Search
  • Org ID
  • PAM
    • PAM - Logging
  • ProView
  • ProView Internal
  • Product Insight
  • Project Tracking
  • RDMS
  • Refinitiv Data Platform
    • Refinitiv Data Platform Libraries
  • Rose's Space
  • Screening
    • Qual-ID API
    • Screening Deployed
    • Screening Online
    • World-Check One
    • World-Check One Zero Footprint
  • Side by Side Integration API
  • TR Knowledge Graph
  • TREP APIs
    • CAT
    • DACS Station
    • Open DACS
    • RFA
    • UPA
  • TREP Infrastructure
  • TRKD
  • TRTH
  • Thomson One Smart
  • Transactions
    • REDI API
  • Velocity Analytics
  • Wealth Management Web Services
  • Workspace SDK
    • Element Framework
    • Grid
  • World-Check Data File
  • 中文论坛
  • Explore
  • Tags
  • Questions
  • Badges