Discussion Board for collaboration on QlikView Management.
Windows Server 2008 R2 SP1
3x Xeon EON E5530 2.4GHz
10 QVW documents
We are daily running through the memory ceiling of our QlikView 11 server, with the QVS consuming 70-80% of available memory. At that point, users are kicked off and unable to reconnect as memory utilization keeps growing. It's not until we stop and restart the QVS service that normal operation is restored. This happens every 18-24 hours.
We only have 10 users and 10 QVW documents. I have previously worked in a 250-user QlikView environment with 8 quad core processors and 128GB memory - same problem.
Does anyone have any recommendations to resolve this problem?
If there isn't a solution to this unsustainable daily operational issue and memory 'leak' maybe it is time to finally look at a competitor solution.
After 4 years of using QlikView, I love the product, but can't believe Qlik hasn't found a sustainable solution to this memory issue.
Unfortunately there's no simple answer to your problem.
There's a lot of points to check because the amount of records doesn't really say much. For example, what kind of data are you loading? How efficient is your data model? What kind of calculations are you doing in the UI? What charts do you have and how are you using them?
As you can see there are many variables at play that can make it seem like a memory leak.
The following links will help better understand the issue, but my best recommendation is to let a Qlik consultant assess the situation and help you find a solution.
Do you have SQL on the same server? Please post the QVS logs and that will give you an idea about the memory issue. It could be your shared file. Are you using Plugin. Make all your users are on the same version as the server. What version of QlikView are you on?
How frequent are your reloads? It could be that there is insufficient RAM to support your users accessing the applications, and also running the reload process running during the day.
I would suggest running an app to view your QV logs and see what RAM is consumed when your reloads run without users accessing the applications, and then how much ram is consumed by user access. This may help identify if the issue is in optimising your load scripts, optimising your chart expressions, or even simply changing your reload schedule.
The documents are no more than 100MB each. There are 12 QVW's.
They are all on the same server.
This is not a new problem, but it has gotten worse in the past month after we increased the frequency of the reloads.
Do you have SQL on the same server?
Please post the QVS logs and that will give you an idea about the memory issue. It could be your shared file.
Are you using Plugin.
Make all your users are on the same version as the server. What version of QlikView are you on?
Both server and clients are on the same version: QV 11.20.12235.0.