topic Re: Making the application faster in QlikView

Making the application faster

nigel987 — Mon, 26 Jan 2026 18:19:17 GMT

Hi,

I had a data model consisting of the table 'Anzeigen'. This table mostly contained IDs (numeric values) e.g. SourceID or AdStatus. The description of those IDs (characters) was stored in the linked tables Source and AdStatus. There is a image of the relevant part of the data model attached.

I heard that the application performance can be improved by reducing the number of linked tables. So I created QVDs which now contain a table 'Anzeigen' with the columns SourceDescription, AreaID, AdType, AdStatusDescription, ... (hence I replaced the numeric field SourceID by the character field SourceDescription, and AdStatus by AdStatusDescription).

The result of this test was:

The generatin of the QVDs takes longer
The application size is bigger
The application is not faster at all. I would say that performance has remained stable

My question is: Was the assumption wrong, that application performance can be improved by reducing the number of linked tables?

Many thanks in advance for every comment.

Kind Regards

Re: Making the application faster

himanshi — Mon, 16 Nov 2015 09:59:13 GMT

yes, minimum links and table reduce the time. and most of the times it depends on your table and what database you are using.

Regards,

Himanshi

Re: Making the application faster

Anonymous — Mon, 16 Nov 2015 10:03:38 GMT

go through following threads:

improving QlikView performance

what is performance tuning in qlikview project?

Reg:What are optimization techniques available in QlikView?

Advanced performance tuning techniques into QV.

optimization techniques for qlikview

Re: Making the application faster

tamilarasu — Mon, 16 Nov 2015 10:14:51 GMT

Hi Nihal,

Yes, It depends on the type of schema which you used.

Re: Making the application faster

nigel987 — Mon, 16 Nov 2015 10:41:51 GMT

Hi Balraj,

thanks for the collection, but I don't really need general help regarding performance improvement. I think I already follow most of the stuff like:

- store data from sourced in QVDs and use of them in the application

- store expressions as variables

- use of variables in objects

- use of linked tables

I was just interested explicity in the difference between Snowflake and Star Schema (see post below). Nevertheless, I tried Rob Wunderlich's Document Analyzer Search Recipes | Qlikview Cookbook and it was useful. I can recommend it to anyone else!

Re: Making the application faster

nigel987 — Mon, 16 Nov 2015 10:44:39 GMT

Hi Tamil,

thanks for the overview. I can add the following:

- QVD generation for Star Schema takes longer than for the Snowflake Schema (at least in my case where I had to replace numeric values by the actual character string)

- QVW files with Storage Schema are bigger (in my case)

Re: Making the application faster

nigel987 — Mon, 16 Nov 2015 10:45:40 GMT

unfortunately I did not see any improvements. all my data is stored in QVDs

Re: Making the application faster

tamilarasu — Mon, 16 Nov 2015 10:47:36 GMT

Can you post your Table view screen shot here.?

Re: Making the application faster

tamilarasu — Mon, 16 Nov 2015 10:50:46 GMT

Hi Nihal,

Nihal Cakir wrote:

- QVD generation for Star Schema takes longer than for the Snowflake Schema (at least in my case where I had to replace numeric values by the actual character string)

Do you use more left Joins in your file? If yes, try to use Mapping load and it will little faster.

Re: Making the application faster

nigel987 — Mon, 16 Nov 2015 10:55:32 GMT

The yellow highlightes fields are the once that I directly added to the main tables 'Anzeigen' and 'Login' so that I could get rid of the tables Source, AdStatus, LoginStatus and PaymentStatus.

Re: Making the application faster

nigel987 — Mon, 16 Nov 2015 10:56:31 GMT

HI Tamil,

will the reload be faster or will the application (refreshing of objects when chanfing filters) be faster?

Re: Making the application faster

tamilarasu — Mon, 16 Nov 2015 11:00:33 GMT

Hi Nihal,

Mapping load is related to background loading of the data. I guess you are using left join, Since you are mentioning that the QVD generation is slow. There are many factors that affect the performance of charts. Replace If statement with set analysis for expressions. You should read the below thread.

*** 6 Weeks in to QV Development, 30 Million Records QV Document and Help Needed!!! ****