Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

QVS server process memory useage

Hi everyone,

We have a dedicated QV server running version 10 of Qlikview, on windows 2003 with 32gb of RAM. Its also a 64bit environment as well. It does have 64gb of RAM installed and we are waiting on an OS upgrade to make full use of this extra RAM.

The above enables up to 100+ users to use AccessPoint to view a QV document which is about 750mb in size. It is on a schedule to relaod each morning at 7am, with the QVD source files being sceduled to reload an hour earlier.

Curently we are being forced to connect to the server and manage the QVS process. Having terminated teh process earlier today after the reloads (it was showing around 12gb memory useage in task manager) it is already back up to 7.5gb. We have to use the server for development due to local performance issues on desktop PC's which seems to contirbute further to increasing the QVS memory usage and it requires constant terminaton during the day.

So, here is my question(s).

Is there a way in the above environemnt to monitor by email, memory useage of this process and warn someone that it needs to be terminate?

Is the above memory usegae normal for the above environment, and will the additional RAM give us more breathing space? (i.e. having a QVS process of 12gb+ is normal)

Hope this gives enough information for some feedback, if not then please ask away.

Phil

3 Replies
Not applicable
Author

Hi,

Had the same issue, and here is a simple way to automatically kill QV / QVS / QVB if using too much memory. QVS can be restarted by adding one more line "net start QVS" , wich does nothing if the process is running fine (meaning not not killed due to excessive memory )

Recommend to set the threshhold around 95% of phisical memory for dedicated QVS servers. Of course, you need to study trends to find the valid memory limits for reload tasks (qvb.exe) and developer tool (qv.exe) in your environment .

Old qlikview posts are gone, so here is a link to Blogger : http://alexandrutoth.blogspot.com/2010/03/qlikview-memory-limits.html

-Alex

Not applicable
Author

Hi Alex,

Thanks for the reply and link to your blog. I have asked out IT team what they think to implementing something similar.

Do you have any negative actions from terminating the process part way through any data loads or devlopment work?

Many thanks

Phil

Not applicable
Author

Hi,

If there is one careless syntetic join over all available data , nothing works anymore . After that particular process is killed, loads / development / QVS work again.

This kills only the offending proceses. Well, those scripts and files are not saved, or might get corrupted.

-Alex