Qlik Community

QlikView Deployment

Discussion Board for collaboration related to QlikView Deployment.

Announcements
QlikView Fans! We’d love to hear from you.
Share your QlikView feedback with the product team… Click here to participate in our 5-minute survey.
Rules, plus terms and conditions, can be found here.
Not applicable

WarningWorkingSet: Virtual Memory is growing beyond parameters ??

Hi

What does this mean?

Warning WorkingSet: Virtual Memory is growing beyond parameters - 1.545(1.400) GB

The server have 4 GB virtual memory to its disposal. Windows 2003 x64

I know that I can change it by altering the working set limits, but I really don't want the QVS to use Virtual memory at all since there is enough physical memory left on the machine.

/Jerry

5 Replies
Employee
Employee

WarningWorkingSet: Virtual Memory is growing beyond parameters ??

This could be caused by an issue with one of the QVW's that the server is opening or an issue with the version of QVS you are running.

Not applicable

WarningWorkingSet: Virtual Memory is growing beyond parameters ??

And in English this means? :-)

Employee
Employee

WarningWorkingSet: Virtual Memory is growing beyond parameters ??

This could mean you have a poorly designed document. You could have "IF" statements that are using more resources than normal, you could have synthetic keys or a number of other things.

jerrysvensson
Valued Contributor II

WarningWorkingSet: Virtual Memory is growing beyond parameters ??

I have found the problem here.

When the customers server supplier moved the qlikview server to another machine. The new machine only had 2 GB of internal memory where the old one had 12 GB.

So basically the server was telling us it had no physical memory available.

We didn't know about the 2 GB and was extremly confused, since we were certain it had 12 GB.

Not applicable

WarningWorkingSet: Virtual Memory is growing beyond parameters ??

Hi.

I'm interested in this topic, as, upgrading from QVS 9 to QVS 10, on same HW, I have faced more and more this event log message.

I can think of my report as a potential cause as it is quite complex with some IF statement, and so on, so the question is: "How could I verify if the report is designed well or badly?" any suggestion?
Take in consideration that I have get rid of synthetic keys, for example.

Thanks

Community Browser