There is really no quick answer to this question. The performance depends on your hardware, datamodell and caluclations done in the script.
In order to reply in more detail, please quantify how much data your are referring to as huge. How many rows and field are you planning to load per minute? Is this a problem in a current QlikView installation or a theoretical question?
If you are experiencing performance problems, maybe you should post a formal support ticket to QlikView support for further evaluation;
Actually qlikview will not work in that scenario.it is failed to operate in real time system.
because you know if you have large data volume and you want to update that data in every minute then qlikview is unable to deploy on server after reloading in every minute.
I agree real-time visualisation can be very hard to achieve in general, but it might not be impossible to get close to it depending on what data you are loading and what define as the real-time time frame.
For example if you have 200 million row in your datat base, it does not mean that you necessarily must reload the entire data volume on each iteration. The reload time would then rather depend on the delta from previous reload, and that delta is then the only thing you load and add on top of the QVD file which the application on the other hand then uses to load its data from.
As I said previously it all boild down to what your data is and what you want to do with it, and it if allows an efficient enough delta loading inline with your time constraint.
Unfortunatley I do not an example QVW at my hands, but please consult the chapter "25 QVD FILES" of the Reference manual. There you can find the different ways a QVD file can be created and maintained. Especially the section "25.7 Using QVD files for incremental load" is related to this type of scenario.
One option for you to evaluate is, build QVDs every night using incremental or delta logic, and during day update data (every few minutes?) using Dynamic Data Update feature on QVS. Sure, you would need a license for dynamic data update and make use of API to update data in QVS memory. This is the best case, I have found, if you are dealing with almost real-time data with very large database where it's impossible to extract data into QVDs in short time iterations.
There is a lot available on Dynamic Data Update subject in QlikView knowledge base. You need to ask your QlikTech salesman or Partner to help you with material.
