QVS server can not release memory

[wenkew186]

hi all,

    i have a problem about the server memeory can not release automantic. it always increase except restart the qvs service.  if  any set issue on QEMC or others. how to solve this issue let release memory itself? any one can help me or get me some suggestion? thanks very much!

   OS: Windows server2008 64 sit

   QVS: 9.0.7440.8

[#2]

i dont think QVS will ever release the RAM.

The idea is to load the data into RAM, so the more you open for the day, the more RAM is going to be occupied.

If your total RAM is greater than your total size of your dashboard, then maybe you wont have a problem.

If you need to reset it multiple time a day, you probably dont have enough ram, else i think it will still good to reset the RAM at the end of business day.

Reset means to restart the QV related services.

I don't know if there's other better way to manage it?

[eduardo_dimperio]

Sorry HIC but i need to disagree, once i had this application that use more that Working Set Limits, even aborting execution, it countinuous allocating memory until crash my server. So we have a Set Limits that not work and a abort button that does not work too. So we need to test our code hoping to not make any mistake cause QS not prevent a server crash for out of memory.

[Chip_Matejowsky]

Hi Eduardo,

I think your scenario was likely due to virtual memory. The attached whitepaper on QlikView Server Memory Management and CPU Utilization states the following:

Like all Microsoft Windows applications, QlikView is dependent on Windows to allocate RAM for QlikView to use. QlikView Server will attempt to reserve RAM when it starts based on the working set limits set in the QlikView Management Console. Once the allowed amount of RAM is exceeded, the QVS process will start purge the cached result sets to ft in any new QlikView applications, new calculated aggregates and sessions’ state information. Please note that QlikView allocates all allowed memory as fast as possible with cached results sets and this does not mean that the QVS will lack in performance once the allowed amount is reached.

If at any time RAM becomes scarce, Windows may, at its discretion, swap some of QlikView’s memory from physical RAM to Virtual Memory (i.e. use the hard disk based cache to in place of RAM). When QlikView is allocated Virtual Memory it may be orders of magnitude slower than when using 100% RAM. This is always an undesirable condition in QlikView and will provide a poorer experience for the users and may be perceived as an error condition by the users. It is critical to realize that the process described above holds true for every Windows based application and is not unique to QlikView.

Hope this helps,

Chip

[eduardo_dimperio]

Hi Chip,

well that sees to me that QS put all blame on Windows, i already used others B.I tools without this problem, buts ok, i'll still using a abort button that not abort at all and not release the memory until crash entire server. And the QS answer probably will be "code better".

[Chip_Matejowsky]

There is no 'blame' here, just a fact since the OS controls memory allocation.

[eduardo_dimperio]

Ok, tell that to my server.

Thanks