topic Are Memory Leaks Normal in QV 10 SR4 in QlikView

Are Memory Leaks Normal in QV 10 SR4

Fri, 24 Feb 2012 22:37:11 GMT

Can someone tell me if memory leaks are a common occurance within other QV 10 SR4 environments?

We are running an application with around 500k records and 170 MB in size. Currently have only around 10 concurrent users. With a fresh reboot the app allocates around 2 - 3 GB which is acceptable. It maintains the allocation for a couple of days and then gradually begins to increase. A couple of weeks later the allocation grows to around 30 GB. When I reported it to support they informed me that it is normal. We typically wouldn't accept having to reboot or restart the service on a regular basis but it sounds like it's our only option.

I appreciate any and all input.

Are Memory Leaks Normal in QV 10 SR4

pover — Fri, 24 Feb 2012 23:31:52 GMT

It is normal that the QV Server accumulates memory as users continue to use QV the memory increases. The QV Server by default allocates between 70% and 90% of the available RAM. A QV document will take up memory and then each users' queries will be cached as they are run. If QV reaches it limit of 90% RAM it will begin to recycle the RAM.

How often do you reload the data in your QV document?

Do you see a reduced performance of QV after a couple of weeks?

Have you run QlikView Ops Monitor (http://community.qlik.com/qlikviews/1076) to study the QV Logs? You can even enable the audit logs to see if the memory increases when certain selections are made or certain sheets opened.

I hope some of these comments help.

Karl

Are Memory Leaks Normal in QV 10 SR4

Sat, 25 Feb 2012 15:36:00 GMT

We reload every 10 minutes as a result of an underlying .QVD incremental load. Performance within the zero footprint seems to be fine until it reaches around 60% (total memory 48 GB) and then it degrades significantly. In some cases it will not respond to clicks.

We do have a ops monitor (for version 10) and it shows for the first three days, after a reboot, stabilized memory usage of around 2 - 3 GB starting on day 4 it starts showing a gradual increase of 1 GB each day after.

The timeout is set to 8 hours (by default) and the dashboard is easily dormant for that long overnight and on weekends. I would expect the memory would be released if not being used for a period of time.

Is it common practice to reboot or restart the services on a regular basis?

Thanks for your comments. It has been very helpful.

Re: Are Memory Leaks Normal in QV 10 SR4

pover — Thu, 01 Mar 2012 01:03:14 GMT

It shouldn't be a common practice to reboot or restart the services on a regular basis.

Is the document preloaded in memory? That could prevent the document from being unloaded from memory.

Actually the document should also be unloaded every time it is reloaded. Since you're dong a QVD incremental load, I assume you aren't using the partial reload option, correct?

Is option "Allow Only One Copy of Document in Memory" found in System->Setup->QVW@servername->Documents enabled?

Is the QVS.exe process consuming the memory or another QV service? I've seen the DSC y Management Console also suddenly use excess resources.

Have you tried to do an audit log to link the increase in memory to anything the user is doing?

Karl

Are Memory Leaks Normal in QV 10 SR4

Thu, 01 Mar 2012 16:28:41 GMT

Hi Karl- I appreciate your assistance with this.

The preload option is set to "Never".

"Allow Only One Copy of Document in Memory" is checked.

The QVS.exe is consuming the most and increases by about a gig a day. It's now around 12 gig. None of the other services appear to be out of the ordinary.

Not sure how to correlate the activities in the audit log to memory usage.

Thanks again

Re: Are Memory Leaks Normal in QV 10 SR4

pover — Tue, 06 Mar 2012 00:57:23 GMT

After looking over what you've described about your case, I don't think it's worth going into the audit log. I think you actually have a good case to report to support and here are my reasons.

Document timeout is not working as described as the document is not unloaded from memory after the defined time.

Cached memory is saved even after the document is reloaded and data is changed.

The last thing I would try to do is adjust the working set from 70% - 90% to see if QV stop at the upper limit and starts recycling memory.

Karl