Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Nov. 20th, Qlik Insider - Lakehouses: Driving the Future of Data & AI - PICK A SESSION
cancel
Showing results for 
Search instead for 
Did you mean: 
schneider2037
Creator
Creator

Data Model Resident Loads

I'm working through overnight performance hits on the QV Server.

One item that I'm seeing is that our Data Model QVWs often have dozens or more of Resident loads against underlying QVDs as well as large SQL outputs from our ERP.


QUESTION: do all of these Resident loads within each QVW really have that much of a performance impact?


Thanks! Jonathan

1 Solution

Accepted Solutions
ychaitanya
Creator III
Creator III

i would suggest to load the data from QVDs wherever possible than compared to using the Resident Loads

and implement exists() with combination of INLINE to implement filters

Thanks

CY

View solution in original post

4 Replies
MK_QSL
MVP
MVP

You can try both

Resident Load

Preceding Load

to find out with one is more effective for performance point of view.

Read below blog..

The Cost of Preceding Load | Qlikview Cookbook

ychaitanya
Creator III
Creator III

i would suggest to load the data from QVDs wherever possible than compared to using the Resident Loads

and implement exists() with combination of INLINE to implement filters

Thanks

CY

schneider2037
Creator
Creator
Author

Git it. Thanks for the helpful link!

schneider2037
Creator
Creator
Author

Gotcha. It also looks like we're fully reloading transaction facts - which is crazy. Why reload transactions that haven't changed since 2012 every night!? Looking to switch the underlying models to incremental. Methinks here lies the major part of the overnight performance hits.

Thanks!