Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Out of Memory v-9

Just a quick question

Objects that worked very well in version 8.5 and prior have "Out of Memory" messages in version 9

Anyone experience this? Anyone have a possible solution for this?

What perplexes me is that I though that version 9 was suppose to have a better calculation engine. I've been experiencing the oposite

5 Replies
Not applicable
Author

Can you name the objects?

Not applicable
Author

pivot table with if then expressions

Not applicable
Author

Ah yes ... those are probably the worst kind when it comes to memory usage. Use a straight table instead when memory issues occur.

If possible, try to avoid if-statements, especially in a pivot table and ones that use texts. Try to do those calculations/statements when loading the data.

Also use SUM rather than COUNT (there are several tricks/tips for this)

There are also ways to aggregate your data before you use it in your charts.

Pivot tables look nice, but are real memory gulpers Wink

Not applicable
Author

thanks,

I guess my perplextion is that this used to work perfectly in 7.0 and 8.5

I'm going to have to add more methods to get this to work

johnw
Champion III
Champion III

I've seen intermittent strange out of object memory errors myself. I can't remember if they were always there, or if they only started appearing when we switched to the server to version 9. In my case, one of the offending charts is a straight table that displays data from a table with only a handful of rows. It has some vaguely complicated pieces, like a dual() function that strings together some fields for a calculated dimension, and one of the columns is a traffic light, and it calculates the color for the caption text and background. But seriously, nothing that would cause an actual memory problem unless there's something seriously amiss.

But I've only seen it happen a couple of times, and no one has complained, so I haven't tried to figure out what is going wrong.