nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ETA code ingest performance

An application was migrated from EMA to ETA (using the example in RTSDK Java), all Java. However, looks like the performance gain is not as expected, although the network statistics show generally good.

The questions:
1. The ETA coding guideline if any (e.g., in EMA, should no logging in the onXXXMsg)
2. Only one machine id, is that possible to make the message consumption to be multi-threaded? so as to accelerate the message ingestion.

Find more posts tagged with

java

eta-api

ema-api

refinitiv-real-time-optimised

refinitiv-real-time

#technology

Accepted answers

Thank you for reaching out to us.

Typically, ETA provides better performance compared to EMA. Please refer to this Real-Time SDKs Performance Test Summary article. However, it also depends on the application logic.

For the guidelines, please refer to the ETA OPEN SOURCE PERFORMANCE TOOLS and document (ETAJ_PerfToolsGuide.pdf) available in the package.

Yes, the client can use multiple threads to process incoming messages, but streams for the same items must be handled by the same threads.

All comments

Thank you for reaching out to us.

Typically, ETA provides better performance compared to EMA. Please refer to this Real-Time SDKs Performance Test Summary article. However, it also depends on the application logic.

For the guidelines, please refer to the ETA OPEN SOURCE PERFORMANCE TOOLS and document (ETAJ_PerfToolsGuide.pdf) available in the package.

Yes, the client can use multiple threads to process incoming messages, but streams for the same items must be handled by the same threads.

Quick Links