Skip to main content
Announcements
NEW: Seamless Public Data Sharing with Qlik's New Anonymous Access Capability: TELL ME MORE!
cancel
Showing results for 
Search instead for 
Did you mean: 
afbraga1
Creator
Creator

Qvw takes longer to reload after upgrade from 11.20 to 12.20

Hello,

After upgrading our Qlikview from the version 11.20 to the 12.20, I have noticed that a qvw is taking more than it used to. I always took in average 2 hours to complete, but now it is taking up to 4 hours. The qvw in question is exactly the same and does noting too fancy. In sum it reads data from a QVD to a table,  two left joins are done to that table and then the data is stored into a new QVD. After, this new QVD is read and two new tables are created: one for value metrics and other for volume metrics. These two tables consist of basically a lot of crosstables  that are joined together. In the end each table is stored into a QVD, being the result of the whole execution three QVD. Also it is worth noting that I am executing the file on both servers through the Qlikview Desktop, there is no Publisher involved.

Best regards,

Andre Braga

Qlikview 11.20 SO Specs:

Item    Value   

OS Name    Microsoft Windows Server 2008 R2 Enterprise   

Version    6.1.7601 Service Pack 1 Build 7601   

Other OS Description     Not Available   

OS Manufacturer    Microsoft Corporation   

System Manufacturer    HP   

System Model    ProLiant DL360p Gen8   

System Type    x64-based PC   

Processor    Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz, 3000 Mhz, 10 Core(s), 20 Logical Processor(s)   

Processor    Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz, 3000 Mhz, 10 Core(s), 20 Logical Processor(s)   

BIOS Version/Date    HP P71, 01-07-2015   

SMBIOS Version    2.8   

Windows Directory    C:\Windows   

System Directory    C:\Windows\system32   

Boot Device    \Device\HarddiskVolume1   

Hardware Abstraction Layer    Version = "6.1.7601.17514"   

User Name    Not Available   

Time Zone    GMT Standard Time   

Installed Physical Memory (RAM)    192 GB   

Total Physical Memory    192 GB   

Available Physical Memory    181 GB   

Total Virtual Memory    287 GB   

Available Virtual Memory    273 GB   

Page File Space    94,8 GB   

Page File    C:\pagefile.sys  

Qlikview 12.20 SO Specs:

Item    Value   

OS Name    Microsoft Windows Server 2012 R2 Standard   

Version    6.3.9600 Build 9600   

Other OS Description     Not Available   

OS Manufacturer    Microsoft Corporation   

System Manufacturer    VMware, Inc.   

System Model    VMware Virtual Platform   

System Type    x64-based PC   

System SKU       

Processor    Intel(R) Xeon(R) CPU E5-2667 v4 @ 3.20GHz, 3196 Mhz, 16 Core(s), 16 Logical Processor(s)   

Processor    Intel(R) Xeon(R) CPU E5-2667 v4 @ 3.20GHz, 3196 Mhz, 16 Core(s), 16 Logical Processor(s)   

BIOS Version/Date    Phoenix Technologies LTD 6.00, 21/09/2015   

SMBIOS Version    2.4   

Embedded Controller Version    0.00   

BIOS Mode    Legacy   

BaseBoard Manufacturer    Intel Corporation   

BaseBoard Model    Not Available   

BaseBoard Name    Base Board   

Platform Role    Desktop   

Secure Boot State    Unsupported   

PCR7 Configuration    Not Available   

Windows Directory    C:\Windows   

System Directory    C:\Windows\system32   

Boot Device    \Device\HarddiskVolume1   

Hardware Abstraction Layer    Version = "6.3.9600.17196"   

User Name    Not Available   

Time Zone    GMT Standard Time   

Installed Physical Memory (RAM)    192 GB   

Total Physical Memory    192 GB   

Available Physical Memory    182 GB   

Total Virtual Memory    241 GB   

Available Virtual Memory    230 GB   

Page File Space    48,9 GB   

Page File    C:\pagefile.sys   

6 Replies
marcus_sommer

Did you a look into the document-logs if the number of records are both the same and to find out if (nearly) all loadings are slower or if certain loadings are increasing in load-times?

- Marcus

afbraga1
Creator
Creator
Author

In fact the reload from QV12 has less number of records since it is using data from a test machine, when compared to QV11 which uses data from production. I can't say all loadings are slower for some reason this one is. Don't know why.

PrashantSangle

Test below

Reload your application in QV12 in test server check task manager, Is it reaching to 100 % CPU utiliazation.

Similarly check in QV11 current production server.

If there any big change in task manger??  Post your observations..

Regards

Great dreamer's dreams never fulfilled, they are always transcended.
Please appreciate our Qlik community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved 🙂
marcus_sommer

Do I understand it right that all loadings are quite ok. but a particular one is significantely slower? Then it might useful to examine this load more closely maybe also by separating within a test-application to find any hint for the why.

Further less data could also lead to wrong loadings therefore I would also copy the source from the production and repeat the testing. Also keep in mind that the different environments could impact the results and not only by RAM + CPU (which seems more potent as in the production) but also by network and storage speed especially if this are not physical machines else VM's.

- Marcus

rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

It appears your V11 machine is physical and the V12 machine is virtual.  This is an apples-to-oranges comparison that is not valid without some serious setup and examination.

-Rob

Anonymous
Not applicable

If you have a valid Qlik support account check the knowledgebase for the following article

Opening documents in QlikView Desktop 12 and later uses more resources while the document is loaded. The consumption goes back to normal when the document is done loading.

This KB does explicitly mentions QV Desktop but I think the same applies to QV Publisher. QV12 transposes rows in a document to columns in memory, so during the load it needs more resources than QV11. Once the loading is complete the resources can return back to normal.