Best practices for Search in Clarity to avoid application overload and OutOfMemory errors


Article ID: 125318


Updated On:


Clarity PPM SaaS Clarity PPM On Premise


Searching in Clarity slows down the application, what are the best practices to avoid heap dumps and OutOfMemory errors?


Release: CODFSS99000-15.4.1-PPM SAAS FedRAMP-Sandbox-Small Environment


Search in PPM is a memory hungry operation that could consume hundreds of megabytes of memory.
Sometimes a user get impatient and opens multiple requests at a time.
Opening a second and third tab or refreshing the page will only resend the request in the same time, and create another long running concurrent request, which will not make things faster but slow them down and even can bring down the application server.
We recommend searching in the application one request at a time, which will ensure the request will proceed at a maximum speed and will ensure the application stability.