Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • TREP APIs /
  • UPA /
avatar image
Question by Mike Slade · Jan 29, 2020 at 02:40 PM · upaperformancelatency

rsslRead and rsslDecode functions latency spikes

Hi

We have measured the latency of our UPA consumer application, and have noticed some unusual behaviour around the rsslRead and rsslDecode functions. Attached is a graph displaying our findings.

Our measurements are showing that the first call of rsslRead takes longer than subsequent calls for message 'bursts' from the network - the blue line in the graph. We assume that this is due to the rsslRead call 'buffering' messages from the network (so the subsequent calls do not perform network reads). However, the rsslDecode functions (rsslDecodeMsg, rsslDecodeFieldEntry...) also all individually take longer when decoding the first message from rsslRead - the red line in the graph. The slower rsslRead call, and the slower rsslDecode functions results in the first message in the input buffer taking considerably longer to decode than the remainder of the messages.

It is worth noting that these 'spikes' we are seeing in the latency of decoding occur even when we fix the size of the messages by using the dynamic view functionality to register interest in only one field. In the attached graph the messages were updates with a single double field.

We would like the latency of decoding messages in our application to be as stable as possible regardless of the message's position in the input buffer - i.e. we would like the lines in the graph to be as horizontal as possible. Please can you explain why these spikes in latency exist, and how we can remove them?

Thanks,
Mike

UPA version - 8.0.0.L1

decoding_latency.png

decoding-latency.png (113.2 KiB)

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 Alex Putkov. · Jul 06, 2020 at 03:20 PM

@Mike Slade

The ESDK development team provided the following explanation for the behavior you observed.

The rsslRead call reads as much off of the wire as possible for efficient processing, which explains the larger amount of time each burst takes.
For encoding and decoding data, this appears to be L2/L3 cache misses in the CPU, either with data or the instruction cache. Since none of the encoding code carries state between full message decoding calls, the development team does not believe there is anything that they can do to mitigate this issue.
If you have further questions, please let us know.

Comment

People who like this

0 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

Performance of UPA

UPA app: Request Rejected: Request message payload not supported on non-private streams

RsslMap not sent as encoded

UPA Port Error

How to release a bound listening socket in UPA

  • Feedback
  • Copyright
  • Cookie Policy
  • Privacy Statement
  • Terms of Use
  • Careers
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Alpha
  • App Studio
  • Block Chain
  • Bot Platform
  • Calais
  • Connected Risk APIs
  • DSS
  • Data Fusion
  • Data Model Discovery
  • Datastream
  • Eikon COM
  • Eikon Data APIs
  • Elektron
    • EMA
    • ETA
    • WebSocket API
  • Legal One
  • Messenger Bot
  • Messenger Side by Side
  • ONESOURCE
    • Indirect Tax
  • Open PermID
    • Entity Search
  • Org ID
  • PAM
    • PAM - Logging
  • ProView
  • ProView Internal
  • Product Insight
  • Project Tracking
  • 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
  • TRIT
  • TRKD
  • TRTH
  • Thomson One Smart
  • Transactions
    • REDI API
  • Velocity Analytics
  • Wealth Management Web Services
  • World-Check Data File
  • Explore
  • Tags
  • Questions
  • Badges