Qlik Community

QlikView Management

Discussion Board for collaboration on QlikView Management.

Highlighted
bnichol
Valued Contributor

QV 12.1 Working Set Limits

Does anyone know if QlikView 12.1 has improved the enforcement of the memory consumption outlined with the working set limits?

We recently encountered a collaboration object that consume over 100GB within 10 seconds.  This pushed our memory consumption to 110% of capacity, triggered memory swapping, CPU usage of !00% for an extended duration and caused the server to freeze until the QVS was restarted.

The same symptoms occurred each time the user opened the document, until we identified them and removed the shared object.

The working set limits were 60% and 80%, but this only caused a message in the event indicating that the working limits had been critically exceeded. 

We are using version 11.2 SR 16, and have experienced this scenario occasionally in the past, but are planning to upgrade to the latest stable version of 12.1.

Are there improvements in version 12.1 preventing the upper working set from being exceeded?  Can the Object size be restricted by some configuration settings?

Regards,

B

1 Solution

Accepted Solutions
Support
Support

Re: QV 12.1 Working Set Limits

Hi Brent,

In my experience, the memory management in QV 12.10 SR3 is pretty much the same as in 11.20 SR16. If a user creates an object which necessitates a large amount of memory to perform the calculations or creates a bad expression resulting in a Cartesian product, etc., Windows may, at its discretion, switch over to paging. This isn't itself a QlikView issue, per se.

See the Release Notes for 12.10 IR (https://da3hntz84uekx.cloudfront.net/qlikview/12.10/12100/QlikView%2012%2010%20Release%20Notes.pdf), section on "What's New in QlikView 12.10." There isn't any mention of new mode of memory management.

Hope this helps

-Chip

Sr. Technical Support Engineer with Qlik Support
1 Reply
Support
Support

Re: QV 12.1 Working Set Limits

Hi Brent,

In my experience, the memory management in QV 12.10 SR3 is pretty much the same as in 11.20 SR16. If a user creates an object which necessitates a large amount of memory to perform the calculations or creates a bad expression resulting in a Cartesian product, etc., Windows may, at its discretion, switch over to paging. This isn't itself a QlikView issue, per se.

See the Release Notes for 12.10 IR (https://da3hntz84uekx.cloudfront.net/qlikview/12.10/12100/QlikView%2012%2010%20Release%20Notes.pdf), section on "What's New in QlikView 12.10." There isn't any mention of new mode of memory management.

Hope this helps

-Chip

Sr. Technical Support Engineer with Qlik Support