-
Thanks @matt_moore
The particular situation we encountered related to the client connecting to the RDB by opening an Analyst session and mounted the HDB. Despite the data being on disk, the sym file was loaded into memory and this was quite large. Other assigned variables were also kept in memory. It was this manual one time action that resulted in the RDB being busy for a length amount of time rather than having a persistent slow subscriber issue. This lead to the build up of data in the TP’s outbound buffer. We availed of .Q.w[] and .Q.gc[] while in the RDB process.
This prompted an internal investigation into memory limits of an Analyst session. The status of this is WIP.
Thanks,
Leah