Preceding load increases size of QVF

[sajalgour2309]

Hello All,

I have been using preceding load since I started working on Qlik and I love it but today I have found one strange thing (I might be wrong but this is why I need clarification )

When I do preceding load, load time is less but size of QVF increases a lot instead If I do resident size is less but time is more. I know all logic of why time is less I preceding but how does it impact on size of QVF i am not aware...

Any idea why this happens ?

Regards,

Sajal

[rwunderlich]

Can you post your script?

-Rob

[sajalgour2309]

Hello Rob,

Script I am using...

Script 1

IOT:
load *,Bus_Unit_Uid+1 as Test;
LOAD
    Bus_Unit_Uid,
    Bus_Unit_Cd,
    Bus_Unit_Nm  as BusinessUnitName,
    Bus_Unit_Desc
FROM XX.qvd
(qvd) ;

Script 2

IOT:
LOAD
    Bus_Unit_Uid,
    Bus_Unit_Cd,
    Bus_Unit_Nm  as BusinessUnitName,
    Bus_Unit_Desc
FROM XX.qvd
(qvd) ;

ARPU:
left join (IOT)
LOAD *,Bus_Unit_Uid+1 as Test   
Resident IOT;

Regards,

Sajal

[sajalgour2309]

It is just a example script. Yeah I know just to understand how it preceding load impact on size of QVF

[rwunderlich]

The difference is in the optimized QVD load.  Script 1 will be an un-optimized load, Script 2 will be optimized  During an un-optimized load, Date and some numeric fields will get converted to dual/mixed fields yielding a larger app. 

-Rob
http://masterssummit.com
http://qlikviewcookbook.com
http://www.easyqlik.com

[sajalgour2309]

Rob,

Can you please explain why a preceding load is un-optimized ?

And if in this scenario should I use script2 as app size has very big difference.

Script 1 - App Size 567.96 MB

Script 2 - App Size 346.56 MB

Should I care about app size or not ?

Regards,

Sajal

[rwunderlich · Accepted solution]

The Script 1 is un-optimized because you are creating a new field in the load. It's not the preceding load per se, but the fact that you are creating a new field in the LOAD.  You would see the same result if you added the new field directly into the LOAD statement. 

For more on the rules of optimized load, see https://community.qlik.com/t5/QlikView-App-Development/optimize-and-non-optimze-load-in-qvd/td-p/311...

In your case, the size difference is significant, which will impact the amount of RAM used.  So in this case, yes, I would care about the size and opt for technique that yielded the small size.

-Rob
http://masterssummit.com
http://qlikviewcookbook.com
http://www.easyqlik.com