Hi - perhaps a dumb question but I'll ask it anyway.
In terms of sizing servers based on data size (& concurrency) I'd previously used the size of the data not the application size which is considerably less. As an example for a recent customer proof of concept I have raw data of approx. 750 mb (.csv files) but the loaded application size is 57mb.
Based on what I've researched & read on the community QlikView is obviously very adept at data compression (even without QVDs) and it would seem that I should be basing the server sizing on the application size not that the data size – is that a correct assumption or is it too simplistic a view?
Its true that QlikView compresses the data to almost 1/10 size, but you you should also know that this compression is when it stores data either in QVD or QVW, but when you open the application the RAM used by the application will be app Size * 4 (this number may increase depending on data model of application) + 10% of app size per user, to store their activity.
So you must consider this factor while deciding sizing of QlikView Server.