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

Announcements
Qlik Connect 2026! Turn data into bold moves, April 13 -15: Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

RAM Utilisation

We are using QVS 8.5 , RAM 32 GB.

My one sheet takes around 30-40 seconds to open; it has various charts on it with big expressions. i want to know if i upgrade from 8.5 to 9, will it reduce the execution time..?

thanks

6 Replies
Not applicable
Author

I suggested to do all calculation in back end

Regards

Ashish Srivastava

Or
MVP
MVP

It may reduce execution time, or it may not - it's impossible to know without knowing the contents of your sheet. Your best bet is to simply try for yourself - install QVS 9 on a server and see how quick the sheet opens.

As a rule of thumb, sheets shouldn't take that long to open - if they do, you are probably either displaying incredibly large straight/pivot tables, or you have some problematic formulas / calculated dimensions. You may want to figure out which object(s) are causing the slow load and see if you can improve that object's performance.

Not applicable
Author

Hi Ashish,

thanks for your suggestion, but we can't do all the calculations in back end.

And are you suggesting no need to upgrade to QVS 9..?

Not applicable
Author

Yes Shoham, you are correct, we are having large straight / pivot tables and some complicated expressions as well. But i read somewhere that QVS 9 has better RAM utilisation. so is it gonna make the process faster..?

Or
MVP
MVP


cherub_imp wrote:
Yes Shoham, you are correct, we are having large straight / pivot tables and some complicated expressions as well. But i read somewhere that QVS 9 has better RAM utilisation. so is it gonna make the process faster..?<div></div>


The only way to know for sure is to test. I had some objects that rendered much, much faster in QV9, and some that were not. If your problem is due to very large straight/pivot tables, odds are QV9 isn't going to fix it for you - you should look into only displaying your tables if the number of rows is reasonable (say, no more than 1,000 rows in a table, or even 10,000).

Not applicable
Author

Escuseme  what you  mean  when  you  say  "do the  calculation in back end." Thanks Claudi Guendelman from Chile