Qlik Sense Optimization
Adoption of BI is closely correlated to response time of result. We have come to expect the response time of ‘Google like’ products and anything much beyond that increases the users’ annoyance level and leads to the project’s failure with usage issues. Health check followed by Optimization of existing installs is a recommended practice every couple of years to ensure that user traction for BI continues.
Enterprises should think about optimization when
- It’s been more than 2-3 years of Qlik usage
- Users start experiencing the slowness while using the dashboard.
What to expect post Optimization
- Optimal use of resources such as CPU and memory
- Increase in the dashboard performance
- Improved user experience and adoption
Our Methodology
- Implement WoWizer to detect the performance issues
- Clean and optimize ETL Layer
- Aggregate the transactional tables to reduce the granularity where not needed
- Implement ODAG and Direct Query for Big Data
- Optimize Frontend calculations to reduce object calculation time
- Implement other best practices
