guaranteedOutputBuffers configuration

f6c

Two consumer applications, one configured with guaranteedOutputBuffers 5000, one configured with guaranteedOutputBuffers 100,000, is the larger one better to avoid the slow consumer (or in other word, the same application may subscribe to more large bunch of RICs without hitting the output threshold breached issue)?

Jirapongse

@f6c

Thank you for reaching out to us.

Setting this configuration on consumer applications will not help resolve a slow-consumer issue. The setting must be configured on the server side (ADS), where it governs the server's buffering behavior. The following definition explains the purpose and function of this configuration

!
! *ads*"${port}"*guaranteedOutputBuffers : 200
!#help
!    guaranteedOutputBuffers: { 1 - N buffers }
!
!    The number of output buffers guaranteed per channel.
!
!    Default value: 24

Typically, if the issue is caused by a slow consumer, it should be addressed on the consumer side (coding). Increasing the guaranteedOutputBuffers value on the server side is unlikely to resolve the root cause; it merely delays the point at which the problem becomes visible.

For more information, please contact the RTDS support team directly for more information.