Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Qlikview is not releasing memory in Server

Hi friends,

Need your help!!

Our server is not releasing memory unless the qlikview services are re-started.

Server is having memory of 512 GB. It is constantly taking up around 400 GB of memory & stays the way it is until the Qlikview Services are re-started. On re-starting the Qlikview Services, the server memory is released drastically & comes down to around 20 GB. Again, over a period of time, it reaches to that zone of around 400 GB & hobbles in that zone.

This in turn is affecting the performance of the applications in the Access Point.

Please help!!

Regards,

Driptodeep

6 Replies
Gysbert_Wassenaar

See these discussions:

Re: 11.2 QVS does not flush memory (?)

QVS server can not release memory


talk is cheap, supply exceeds demand
ramoncova06
Specialist III
Specialist III

adding to what Gysbert already provided

you can create a windows schedule job that restarts the services every night

    net stop qlikviewserver

    net stop QlikviewWebserver

    net stop QlikviewManagementService

    net stop QlikviewDirectoryServiceConnector

rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

Why would you need to restart the services each night?

-Rob

rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

"This in turn is affecting the performance of the applications in the Access Point."

I've not seen using 400GB of 512GB cause a performance problem by itself. Unless...you are running other applications on the server. Are you running reloads when users are logged on? Or running database or other servers on the same box?

-Rob

ramoncova06
Specialist III
Specialist III

I have seen issues where the memory of the server hit's the max threshold and then users are not able to open any document or all they get is a white page and it starts working normal after you restart the services.

this has only happened to me just a couple of times (the issue seems to be with a bad designed QV document ), but if Driptodeep is worry about the memory consumption this could be an option to get a clean server every morning

Bill_Britt
Former Employee
Former Employee

Hi,

If you look at your working set you will see the value low is set at 70%. So, 70% of 512 is 358, so I would say things are working correctly. Also, remember the default document setting is 8 hours.

Bill

Bill - Principal Technical Support Engineer at Qlik
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.