EMA C++ Performace Tools Guide : Appendix A Troubleshooting : A.2 Not Achieving Steady State
 
A.2 Not Achieving Steady State
There are several reasons why a consumer might not reach a steady state:
The steadyStateTime value may be too small. When publishing in latency mode or at high update rates, providers will take longer to process image requests. For example, if steadyStateTime is set to 30s but the provider can publish only 2,500 images per second, the consumer times out before it receives its 100,000 images.
The provider might be overloaded. If the provider is publishing at or near 100% CPU for its configured update rate, it will be either unable or barely able to service incoming image requests, which causes images to trickle back to the consumer.
The consumer might be overloaded.
If using a non-interactive provider application, the provider and consumer watchlists might not match, resulting in the consumer application requesting items that never appear in the LSEG Real-Time Advanced Distribution Hub cache.