Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
The users of my dashboard are reporting long lag times when they are making selections, (Adding dimensions to a chart or filtering data.) There is 18.5 million records of data that are available to chart. Would this lag time be a result of too much data, a caching issue, a server issue, or possibly a combination of these?
18.5 rows is not too much, but your schema design and expressions are important when you have that much volume. The problem may be an undersized server. If true, then I would expect you would see poor performance across all applications.
I would start with tuning the application and identifying the performance hot spots -- expressions that take a long time.
1. Remove large unused fields to reduce the data footprint.
2. Identify charts and expressions that take a long time to calculate, then focus on improving those.
You can use a tool like QSDA Pro or Qlik Telemetry data to help in your tuning.
By the way, is your Qlik server on-prem or Qlik SaaS (Cloud)?
-Rob
http://www.easyqlik.com
http://masterssummit.com
http://qlikviewcookbook.com
18.5 rows is not too much, but your schema design and expressions are important when you have that much volume. The problem may be an undersized server. If true, then I would expect you would see poor performance across all applications.
I would start with tuning the application and identifying the performance hot spots -- expressions that take a long time.
1. Remove large unused fields to reduce the data footprint.
2. Identify charts and expressions that take a long time to calculate, then focus on improving those.
You can use a tool like QSDA Pro or Qlik Telemetry data to help in your tuning.
By the way, is your Qlik server on-prem or Qlik SaaS (Cloud)?
-Rob
http://www.easyqlik.com
http://masterssummit.com
http://qlikviewcookbook.com