Optimize QVW file

[prma7799]

Dear All,

I have one application and It is taking lot of time to open or saving .

Can anyone please tell me how to optimized this application in better way front end as well as back-end.

One possibilities that I will convert all big expression into variable and use it in the application everywhere.

Is this solution is good for optimization or please give me some ideas on this.

Thanks .

[marcus_sommer]

At first check if compression is enabled (tab general in document properties) and then check with the Document Analyzer update 2.7 and The Importance Of Being Distinct.

- Marcus

[avinashelite · Accepted solution]

front-end

1.Push most of the calculated dimensions to script

2.Use set analysis effectively in all your expressions

3.Identify the charts which are taking more time load in the front and add conditional display 

4.If you have huge data then loading will take more time in the front end so load the heavy data chart conditionally

back-end

1. Check your model and the data associations

2. check your joins

3. eliminate unwanted fields from the script

4. avoid Syntactic keys 

[Anonymous]

Converting expressions to variables will make no difference to the time taken opening / saving.

[avinashelite]

As per my knowledge it doesn't ...it will help you to edit your expression easily but in terms of memory I don't think it will help you

[Anonymous]

might be helpful for you?

Best Practices for Data Modelling

[prma7799]

Hi Avinashelite‌,

- Identify the charts which are taking more time load in the front and add conditional display

- If you have huge data then loading will take more time in the front end so load the heavy data chart conditionally

Will this is really helpful to open file on access point?

Thanks

[avinashelite]

yes it will ..

see for e.g. your straight table has 10 years of data .. if you make it conditional to display the tables  on select of any year ..it will display only the selected year data not the complete 10 years so it will load faster.

[Anonymous]

Avinash is correct - it will help.

I do not think it is worthwhile to have more than a few thousand data rows visualized in a front end display table. 

The human brain cannot process that many data rows at one time and scrolling up and down becomes impractical to use sensibly.

But if you do set things up so the display table contains a few million rows, QlikView will still load them all, take ages doing doing so and chew up loads of RAM - assuming you have enough RAM otherwise it will start paging [which is a performance nightmare] and ultimately collapse when you run out of RAM + Page File.

[avinashelite]

if you have got the answer please mark the helpful and correct answers and close this thread ... so that it will be helpful for others who are having the similar question