We request an enhancement in terms of memory tuning to Digital.ai Release to prevent container memory exhaustion while rendering large amount of data in activity tabs generated by high-frequency tasks. So, if we load multiple activity tabs with large amount of data it consumes entire memory of container and hence results container crash Our ServiceNow integration plugin performs repeated CRQ status checks (e.g. 1000 times status of CRQ in ServiceNow), which produces extensive logs. When the Release UI loads these logs, the container (10 GB RAM + 12 GB swap) consumes memory extensively and crashes, which results in slowness of UI and sometimes making the UI inaccessible.
Currently, excessive log output generated by repeated tasks leads to:
1) UI becomes extremely slow or unresponsive for affected tasks.
2) Excessive JVM heap usage.
3) Log retrieval becomes impossible.
4) Inability to open or view task logs or releases.



We suggest you to provide a change that cleans active jvm memory (Garbage Collection) when operation is completed.
Also, please provide a pagination view of activity logs, so that it does not load entire logs at one time which may result high consumption of memory.

We already have discussed this case with your support team in below Support request:
https://support.digital.ai/hc/en-us/requests/236923

by: Rahul R. | 4 days ago | User interface