Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
nigel987
Creator II
Creator II

Making the application faster

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

11 Replies
himanshi
Contributor III
Contributor III

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

tamilarasu
Champion
Champion

Hi Nihal,

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

nigel987
Creator II
Creator II
Author

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!

nigel987
Creator II
Creator II
Author

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)

nigel987
Creator II
Creator II
Author

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

tamilarasu
Champion
Champion

Can you post your Table view screen shot here.?

tamilarasu
Champion
Champion

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.

nigel987
Creator II
Creator II
Author

TableView.PNG

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.