Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi I have installed Qlik sense on a virtual box in a Linux server , but the performance of the dashboards keeps on fluctuating whereby the engine service would stop and even after restarting it, the Utilization of the CPU is consumed to 95% and above. My query is, how would I ensure that I configure qlik sense on a Virtual machine and still use the same server for other activities that will run on linux and maintain a stable Qlik environment?
if you plan to have multiple platforms on your linux server ,make sure to check the requirement for each of them including the operating system.
Each platform should have it own dedicated processor/core and ram
Hello @hillarynyawate
Make sure you also check the engine service memory threshold. See the link below: Qlik Sense Engine - How the memory hard max limit ... - Qlik Community - 1717228
In the link below you can also check a list of requirements to run a healthy Qlik Sense Server.
System requirements for Qlik Sense Enterprise ‒ Qlik Sense for administrators
Regards,
Eduardo Monteiro
Well then does this means that now Qlik has to be on in its own server for optimal performance and scalability?
Ok understood, thanks for the insight @anderseriksson
Sorry for a late answer, been very busy last weeks.
Yes own server has always been the optimal for performance and scalability.
It is for every program, even "MS Mines".
Kidding aside shared servers can work but then need to be dimensioned for the shared peek load.
Databases and Qlik (which is an in memory database essentially) both need memory.
When replying to a question both databases and Qlik needs CPU.
If these things happen in parallel you are going to run out of resources.
Hi @hillarynyawate you really should review this document for a clear description of memory and CPU usage
The Qlik Associative Engine memory management and CPU usage
And this article for best practices when deploying to a virtualized environment
Virtualization-Best-Practices-In-QlikView-And-Qlik-Sense
hope this helps