Hi @exchange-notifications, Both RFA and rmdstestclient receive data in an identical manner.

The reason you are seeing huge latency in your RFA application is that your application probably is a slow consumer. This means, that the events are sitting in your applications dispatch queue for a very long time at market open hours - when the volume spikes.

The solution to this problem is to optimize this event processing loop. If the applications falls too far back, then the market data system (ADS) will drop the connection.

@exchange-notifications

You can also turn on the RSSL trace log using the RFA configuration provided in this post

https://community.developers.refinitiv.com/questions/6057/activate-full-message-logs-for-rssl-connections-in.html

It will log the RSSL message that the RFA internal layer(UPA/ETA) sends and receive with timestamps to compare it with the application layer. But please note that you may get a huge RSSL Trace file if you request many RICs, and it has a very high update rate.

Also, please verify if you have any time-consuming or I/O tasks inside the processEvent method. It can block RFA to dispatch the next event from the RFA event queue. If it's a slow consumer case, you may see the time for the next event keep increasing when compare with the app that processes the fields and print it to the console. As far as I understand, the rmdstestclient parse the field and print it to console, and it works like a simple ETA/UPA consumer app.