topic How to tell the size of a QVW on the server? in QlikView

How to tell the size of a QVW on the server?

Mon, 26 Jan 2026 18:19:17 GMT

I have a QlikView Server (v10) that is serving 10 QVW applications. Server and Publisher are running on the same machine. The total size of all of these applications on disk is ~300MB. However, when I look atht he QVS process in Task Manager, it is consuming ~19GB!

Is there any way to tell how this memory is being distributed among the QVWs, or to tell which one is so big?

How to tell the size of a QVW on the server?

danielrozental — Mon, 05 Mar 2012 17:58:09 GMT

No, there is no way.

It's a combination of largest application and more selections being done, hence more cache being used.

You should look into restarting your services periodically, even daily if possible.

How to tell the size of a QVW on the server?

deepakk — Tue, 06 Mar 2012 07:48:00 GMT

hi ,

Try configuring the System monitor. This might give you the picture of RAM utilization over the priod.

http://community.qlik.com/qlikviews/1029

Deepak

How to tell the size of a QVW on the server?

erichshiino — Tue, 06 Mar 2012 11:29:10 GMT

Hi,

When you store a qvw, the default setting is a high compression format.

When you actually open it, it will consume more RAM.

If you perform a reload during the day, when the users are using the applications it will also consume more memory.

As a rule of the thumb, you can consider that after the first user accessing a document, each additional user may consume 10 - 15% more RAM.

If you are able to install QV Desktop on the server, you can open the files one by one to check (more or less) which one requires more RAM.

Hope this helps,

Erich

How to tell the size of a QVW on the server?

Tue, 06 Mar 2012 14:53:36 GMT

Thanks Erich.

It turns out that the reason QVS was using so much memory was because of the Performance settings in QEMC. The machine has 32GB of RAM, and the memory limits were set to 70% - 90%.

After reading up on this, it looks like QVS will try to grab as much memory as it can until it reaches the lower limit. Then, it will grab more memory as necessary until it reaches its upper limit. When it reaches its upper limit, it will start resuing memory from its cache.