Performance problems with QVW11

[ramonarcusa36]

Hello to you all.

First, I will introduce our server specs: Windows Server 2008, multi-core processor with 14 CPUs (2,53Ghz each), 24GB RAM. We moved from QV10 to QV11 one week ago (problems later mentioned appeared before upgrading).

We have built several QlikView documents. One of them is, by far, the biggest one, weighing over 2GB of hard disk space. This one is also the most accessed document. We activated the Preload checkbox, and from that moment on, it looks like the document opens faster most of the times.

Over the last few weeks, we have been experiencing some performance problems. Some times, QlikView "freezes" for about 10 or 15 seconds when users try to perform any action (make a selection, change the current field in a cyclical group or whatever). When things go fine, every process or calculation made by QlikView barely last less than 1 or 2 seconds, so 10 or 15 seconds is totally unacceptable.

We have stated that, as day advances, VMCommitted and VMAllocated increase, and never decrease (Status->QVS Statistics->Performance). In Document->Performance, we configured the Document Timeout to 1 minute, so QlikView could release memory as soon as nobody is working with the document. However, it looks like it doesn't release any byte. Does QlikView ever release memory resources? It looks like it just releases memory overnight (perhaps due to the 480 minutes set as default in Document Timeout for the Server), because when we come to work early in the morning we can check that memory has been almost completely released.

As far as I know, QV allocates memory for approximately a 10% (that could be more or less depending on many factors) of the document for each user accessing the document. When do those extra bytes of memory get released? Does it depend on the Preload checkbox? I mean, if I have the Preload checkbox activated, does that interfere with the release of the memory allocated because of every user access?

Thank you all for your support.

[Bill_Britt]

Hi,

Take a look at this document and see if this will help you any.

Bill

[Ricardo_Gerhard]

When the document time is reached, the memory allocated to document is release. The session memory of users isn´t release after sessions time-out. To release memory you want to restart Qlikview Server Service.

It´s WAD issue, work as design.

[#4]

But right now, I am in a customer site, and even if I set the Document Timeout setting to 2 minutes, and I opened 1 document and used up around 24GB of RAM out of my server 32GB.  I closed the browser, and then wait for 4 minutes, and opened another document, I observed that the memory occupied by previous document did not get release at all!  Now, the second document cannot be open and it just prompted "No Connection"!  Please help!  It's urgent.

Ivan

[#5]

Sorry, I found the reason.  The session is still there because I just close the browser.  If I click on the "Close", the server memory can be released in around 1.5 minutes when I set it to be 1 minute.