Working Set limits don't stop QVS.exe usage; 9 SR4

[#1]

This is urgent that we verify the Working Set limits work to stop memory allocation caching.

We will not purchase additional licenses until this feature is confirmed working in our environment.

I've adjusted our settings to 21/21/10%. Our server has 64 GB so QVS.exe should be limited to 13.44 GB

After adjusting the Working Set, we clicked around via AccessPoint.

QVS.exe climbed to 14.4 GB.

The working set settings are not stopping memory utilization. How do we adjust to make these settings work as designed?

Is a reboot required after adjusting the settings?

Thanks

[#2]

You need to stop and start the QlikView Server service. Even if it doesn't say so.

[pablolabbe]

Did you solved this problem ?

[#4]

I am having exactly the same problem too.

I was running on a 64GB RAM server. Escalated to Qliktech and they have recommended me to update the RAM. So now I have upgraded to 128GB, but the problem is still the same. The memory keeps increasing and has never dropped unless we restart the QlikView Server service.

Our working set is 70% to 90%. Now our RAM is hitting 81% and still no sign of coming down.

[Bill_Britt]

To me this appears to be working normally. See if this document will help you any.

Bill

[korsikov]

I read your document. There are issues.

If the computer where the QVS runs to run QV Desktop with the application that will take aboee half the RAM. But in this case is contrary to install working log limit of 70%. How to behave in the server process? what process will consume more memory? my experiments shows that the working limit of the two processes becomes equal 50 to 50

It turns out that the working limit is not a guarantee allocation of memory to the server process

Thanks in advance for your answers

[Bill_Britt]

Hi,

To start our server require is that no other software is to run on the same server as QVS. Even if you set the limits it is up to the OS to enforce them.

Bill