topic Memory Issue in QlikView

Memory Issue

pkelly — Wed, 19 Jan 2011 16:17:11 GMT

Every now and again our users (who are access their QlikView reports via the ie plugin) get a message saying that they cannot open the report.

If I log in to our server and end the task QV.EXE*32 and ask them to try again - they are then able to see the report ok.

The QV.EXE*32 task has a whack of memory allocated to it which i think is causing the issue - terminating free's up this memory.

Could this be something I am doing wrong within my reports / scripts?

In my QVD table scripts - after my store command I am always dropping the table - Is there something else I should / can be doing?

Any guidance greatly appreciated.

Regards

Paul

Memory Issue

rwunderlich — Wed, 19 Jan 2011 20:38:35 GMT

There shouldn't be any qv.exe tasks running on the server. Are you scheduling qv.exe command line reloads on the server?

-Rob

Memory Issue

pkelly — Wed, 19 Jan 2011 23:22:53 GMT

Hi Rob

I have made a typo in the most important part of the post...

The task is QVS.exe*32

I think that this is the QlikView server but it just keeps grabbing memory and doesn't appear to release it.

When it gets to abour 1.2 Gb we get this issue and I need to end the task - it automatically starts back up again which is fine.

Just worried that this is either something that I am doing wrong or we have a problem with our server set up!

Regards

Paul

Memory Issue

rwunderlich — Wed, 19 Jan 2011 23:39:16 GMT

Hi Paul,

That's pretty normal to have QVS using 1.2GB. I'm assuming your server has several GB of RAM. QVS will use memory to hold documents -- even after users disconnect -- until the docment timeout is reached. Memory is also used to hold cached results.

In your QEMC console you can view:

- How much memory is allocated (Performance tab)
- What documents are currently loaded in memory.

Back to your original problem, I suggest looking at the QVS Event log and the Windows Event logs for clues as to why the open failed.

-Rob