Skip to main content
Announcements
Qlik Connect 2025: 3 days of full immersion in data, analytics, and AI. May 13-15 | Orlando, FL: Learn More
cancel
Showing results for 
Search instead for 
Did you mean: 
Marcio_Campestrini
Specialist
Specialist

Qlikview desktop memory consumption

I wonder if someone can help me. I have a question.

Recently we have begun to develop some applications that, after charging, are generating qvw files of about 1Gb. When I open these files in Qlikview in my compputador quickly the memory of the machine hits the occupied 11-12Gb (of a total 16Gb).

My question is if this is normal or if there is anything we can do about it. If this scenario is common, we will purchase equipment with 32Gb memory.

I know it's not possible to say exactly the problem and give a solution for this is tricky since you do not have access to the structure, but the idea here is just to understand what may be happening to chart a future planning.

Márcio Rodrigo Campestrini
1 Solution

Accepted Solutions
ashfaq_haseeb
Champion III
Champion III

Hi,

have a look at below posts.

http://community.qlik.com/message/455415#455415

http://community.qlik.com/message/444168#444168

http://community.qlik.com/message/455396#455396

http://community.qlik.com/message/519348#519348

Rest all depends on logic you build. Try to push all logic to backend.

Use 3-tire architecture to build your application.

Make front end application or layer 3 as optimize as you can.

Regards

ASHFAQ

View solution in original post

3 Replies
ashfaq_haseeb
Champion III
Champion III

Hi,

have a look at below posts.

http://community.qlik.com/message/455415#455415

http://community.qlik.com/message/444168#444168

http://community.qlik.com/message/455396#455396

http://community.qlik.com/message/519348#519348

Rest all depends on logic you build. Try to push all logic to backend.

Use 3-tire architecture to build your application.

Make front end application or layer 3 as optimize as you can.

Regards

ASHFAQ

avinashelite

Hi,

As we know Qlikview is a In-memory tool, so based on your application size Ram consumption is decided.

In your case its correct, it occupies so much because your app size is more than 1 GB. Try to do performance tuning on your app so that the file size will get reduce.

EG:  *Do all the complex calculation in the script.

        *Eliminate the unwanted fileds etc

shane_spencer
Specialist
Specialist

In short the size of a Document in Memory will be roughly 4.25x the size it is on Disk. That does not take in to account any cached results created by user activity.