Depends on which part of QlikView you're talking about...
The server has working set limits which govern how much memory it uses (in QEMC, go to System, QlikView Servers, select your server, and look in the Performance tab.)
I don't believe there are similar settings for either the reload / distribution engine, or for QlikView desktop.
It is true about the working sets, however, the paging wont stop, since this is not Qlikview responsibility, it is the OS. We can lower as much the Working set, which will degrade Qlikview performance, or leave it as is, but if you see memory paging, since Qlikview reserves 90% of the memory and if you have other resources in need of memory the paging will take effect, regardless.
Now, in that case it is best to do a health check on your machine, and ask the questions why my server is paging to disk? Is because you have to many users? by that I will consider a bigger machine with more resources and splitting the services.
Or you have low number of users, but high memory consumption? In that case I would review or do a health check to the documents, that can improve the performance with lower memory consumption.
You can check the Scalability team page with different tips:
Thanks for the tips Giuseppe Novello,
The question is :
1. Will Qlikview work properly if we "switchOff" page file completely from the OS settings?
We have a 3GB app with 50 user licence and 160 GB RAM..Concurrent users are never more than 15
2. Is it possible to do this setting in the QlikView server itself rather than doing it in OS?
We are on QlikView 11.20 SR5 in a Virtual Environment.
Till recently I had always suspected page file to slow down the performance, but a couple of days ago it "Cached" so much of data in it that it almost crashed the server.
Thanks and Regards,
1. It's not that QlikView might or might nor work, but rather that system would likely become unstable
2. There is no such setting within QlikView
The keys in this setup is that you are running a virtual environment.
QlikView will adhere to the working set limits as mentioned by others,
but if that RAM is not physically available at any given point it will force the Hypervisor (often VMwares ESXi, but depending on vendor for VM) to page to disk. At this point QlikView will not be able to run well as the in memory technology will have to query a slow disk ( yes it's slow even if SSD).
The general recommendation when running QlikView in virtual environments is to dedicate all hardware to the VM instance running QlikView.
1 physical server with 256 GB RAM running VMware and two Windows instance with QlikView on one.
QlikView working set limits set to: 90%/95% out of the dedicated 192GB, yielding 172,8/182,4GB as actual RAM limitations.
Make sure that all 192 GB RAM is dedicated to the QlikView VM instance with no dynamic allocation of RAM, so for VMware ensure to use the "Reserve all guest memory (All locked)"
For VMware you can read more about how to do it here:
Overallocating CPU resources (sharing CPU) is less dramatic for QlikView, but it's recommended to forcefully allocate CPU resources and avoid sharing as much as possible for better performance.
Hampus von Post