reducing input data is easy to say - usually when you build a QlikView_app, you are supposed to show all of the data.
Still, you have a point - there are often fields which are not needed (in which case there is a "document_analyzer" that will tell about fields not used on the UI - and you might be able to filter for only a certain timerange - the latter possibility depends on the users' wishes...
Another point you could try: You say there are calculated dimensions - those are resource-heavy. Try to think of a way you can calculate these dimensions in the script so that on the UI you can access them as regular fields.
Reducing data size--> was a suggestion to test whether the error goes off after doing that. So that we can be sure that its memory problem. Then we can request for upgrading machine hardware to process huge data.
Everybody in the world knows that we need to use all input data according to user requirement in the application.
It is a great way of identifying what in your qvw is consuming what RAM. Then when you know the cause of the issue defining the solution is a lot easier.
