This content has been marked as final. Show 2 replies
I've just noticed an interesting issue:
I've developed a QVD generation scripts and have tested it in from QV desktop. The result QVD file (QVD1) was successfully loaded into QVW UI application.
After the QVD generation file was published, the QMC task was executed which produced another QVD file (QVD2).
There is slight difference in actual QVD files sizes (2,594,121 KB for QVD1 vs. 2,594,122 KB for QVD2) which caught my attention.
But the main surprise came when I've reloaded these file into the UI application.
When the QVD2 file was loaded, the result QVW file significantly bigger (1,518,133 KB in size vs. 1,125,113 KB size of final UI QVW based on QVD1 file).....
Both files contain the same number of records (24,099,984) and there is no difference in UI between these applications.
Please note that I've loaded the UI QVW from QV Desktop in both cases, so the size difference is caused by the method the QVD was created, looks like. The QVD contains one table with 106 fields.
Did some testing with dummy data and the results are similar. The size difference depends on the number of fields in the QVD file.
Here is the summary:
|Environment||# of fields in QVD||# of Records||QVD size||Result QVW size||Diff|
|Desktop||2||10,752,000||209,768 KB||124,789 KB|
|QMC||2||10,752,000||209,767 KB||124,808 KB||19 KB|
|Desktop||18||10,752,000||2,389,992 KB||1,713,190 KB|
|QMC||18||10,752,000||2,390,009 KB||1,714,841 KB||1,651 KB|
Just wondering what QV is doing to the Output QVD file if it inflates the size of QVW file that uses it??
I would appreciate experts' advice.