after installing QV12 in a new server environment, we unfortunately have often performance problems regurlarly and in a not systematic pattern and often ad-hoc in not scalable time-frames (for example apart from regular script runs).
With reagrds to server metrics (CPU, Memory, Disk) we cannot determine the exact reason as technical critical thresholds are not exceeded.
In a very simple heuristic approach, I have the suspect that a single frontend user (in the web application) might cause the crash by using existing documents and displaying all dimensions in a object, without setting selection filters upfront.
Is this possible or can we exclude my suspect? If possible, how can I analyze my suspect more deeply?
I would suggest a solution is to upgrade your hardware with much much more memory. We used to crash similar but by not by a single user. But during the peak hour every day when users log in together and the apps were reloading at the same time like at around 9 am. After we upgraded our memory in server from about 120gb to 240gb. It solves the crash issue like magic! Also the VM better o be solely installed and used within a physical machine to ensure the memory is only being consumed by the Qlik server's VM.
You may monitor the your memory consumption in QMC's statistics - performance as well as your server's Windows task manager - performance to check whether the memory was being consumed over 90%.
AGree with the other posters that additional RAM or server hardware upgrade would very likely improve QlikView performance. QlikView is an in-memory application so addtional RAM will always help.
Best Regards
Principal Technical Support Engineer with Qlik Support Help users find answers! Don't forget to mark a solution that worked for you!
