I have restarted the Server now its fine but i want to know the reason for this. Because i am developing at client place and after sometime will move from here if the same thing happen again it will create problem to the users.
I want optimized solution that can ensure that problem will not appear in future.
Hi Lalit Chaudhary did you find a way to solve this becasue we have a similar situation when the memory is never released but is bogger the problem due the qvw size weights 200 MB aprox. and the memory consumed is a lot.
Qlikview server has been designed to catch most of the data in memory. So, that the end user experience is better and gives results on the fly.
So, as more and more users open the applications, all of their states are being catched into memory, the benefit is of performance. so, if the same calculation is needed again it can generate results faster.
This catching mechanism is handled by Qlikview server. It will only release the memory if it needs it back.
and as Qliktech always recommends that your Qlikview server system should be for Qlikview only.
It is by design only.
one point here to notice is that
Qlikview server assumes that it has reserved physical memory upto the low limit working set.
This low limit of physical RAM can always be changed, by default it is set to 70%. Also, option is there to set maximum amount of physical RAM it is allowed to use.
These settings can be changed from management console.
Hope, it makes sense.
Still, if you believe that in your case it is not performing as per your expectations then you should contact support.
Hi Ashutosh Paliwal the post you wrote above comes from an article or a document? if so, can you share the source due we need to exlpain to a users about this memory handling with a valid argument. i would appreciate your help,