topic Re: Does reloading qlikview dashboard manually takes more memory than reloading via QMC? in QlikView

Does reloading qlikview dashboard manually takes more memory than reloading via QMC?

Mon, 26 Jan 2026 18:19:17 GMT

Hi,

I wanted to know if reloading qlikview dashboard manually (via your username) on the development server takes more memory (there are other developers also logged into the same development machine) than reloading it via QMC.

Thanks in advance.

Regards,

Janaki

Re: Does reloading qlikview dashboard manually takes more memory than reloading via QMC?

Bill_Britt — Mon, 19 Jan 2015 20:31:56 GMT

Hi,

I would expect the memory for reload would be about the same.

Bill

Re: Does reloading qlikview dashboard manually takes more memory than reloading via QMC?

Mon, 19 Jan 2015 21:00:56 GMT

Hi Bill,

Thanks for replying.

For heavy dashboard which takes more than 1 hour, would you recommend a manual reload or a reload from QMC.

Also does running via QMC runs the task in the background which ends up using less memory.

Regards,

Janaki

Re: Does reloading qlikview dashboard manually takes more memory than reloading via QMC?

Bill_Britt — Mon, 19 Jan 2015 21:07:30 GMT

Hi,

The reload with publisher is almost the same as running the desktop. If you look at the services, you will see a QVB.exe process running. This is basically the desktop QV.exe without a GUI. Reloads should be schedule during the day/night when you have less activity on the server.

Bill

Re: Does reloading qlikview dashboard manually takes more memory than reloading via QMC?

Mon, 19 Jan 2015 22:58:23 GMT

Hi,

I think Bill have cleared the most of the things regarding the topics but I still like to point out that I think you should reconsider your setup and instead look into divided environment for dev and the QVS as you current setup will result in regular problems that will cost you in the long run.

Re: Does reloading qlikview dashboard manually takes more memory than reloading via QMC?

Mon, 19 Jan 2015 23:46:25 GMT

Hi Hampus Andersson,

Can you further explain what sort of problems do you expect we would face in the longer run?

Regards,

Janaki

Re: Does reloading qlikview dashboard manually takes more memory than reloading via QMC?

Tue, 20 Jan 2015 00:02:24 GMT

Hi,

The most noticeable problems are and will be the use of resources. The QVS function best in a environment where it allowed to used the maximum of all resources, a scenario that you will not be able to provide in a mixed environment where you also are doing development and development related reloads.

If you plan to scale the use of the QVS as a platform to publish documents to your end users (and not just as a reload-platform) will you also have an increasing use of the servers resources with every logged in user.That means that the logged in users will affect the developers work, and the developers work will affect the end users usage experience. So I would say it sounds like a lose-lose saturation but I assume you are aware of the problems are you whent down that path in the first place.

Re: Does reloading qlikview dashboard manually takes more memory than reloading via QMC?

Bill_Britt — Tue, 20 Jan 2015 00:07:55 GMT

Hi Hampus,

You are correct if they have the money to invest into additional Hardware.

Bill

Re: Does reloading qlikview dashboard manually takes more memory than reloading via QMC?

Tue, 20 Jan 2015 00:42:14 GMT

Hi,

Well we have been facing memory starvation issues and due to that our developers have been disconnected from the development server quite a few times. So until IT kills the process that's eating up the memory the server won't allow any of the developer to login and work on their stuff. Same goes with the end user.

We thought we had a high end server (256 GB RAM) and it would be able to manage the load, but the way qlikview works (in-memory) it is not helping much.

Thanks for the comments.

Regards,

Janaki

Re: Does reloading qlikview dashboard manually takes more memory than reloading via QMC?

Tue, 20 Jan 2015 01:07:43 GMT

Hi Bill,

Would you recommend having Development environment for the developers to login (One single server or different instances for every developer) and work on their QV applications and have the dashboards published on another separate environment (QA) with just the publisher. The Production environment will be completely separate.

What are your thoughts on this sort of server architecture?

Regards,

Janaki

Re: Does reloading qlikview dashboard manually takes more memory than reloading via QMC?

Bill_Britt — Tue, 20 Jan 2015 01:55:42 GMT

Hi,

What is the process that is eating up all the memory? Could this be caused by a poorly designed data structure?

Bill

Re: Does reloading qlikview dashboard manually takes more memory than reloading via QMC?

Anonymous — Tue, 20 Jan 2015 19:09:07 GMT

I would suggest your developers work on a seperate server to that running the QlikView Server Windows services.

They should then be able to connect into it with RDP. Developers by definition do things that are initially untested and an accidental Cartesian Join can gobble up RAM, other things can chew up CPU.

Re: Does reloading qlikview dashboard manually takes more memory than reloading via QMC?

Peter_Cammaert — Tue, 20 Jan 2015 23:26:14 GMT

Well, I can see where this is going, and IMHO it's not the solution that fixes all - it never will be.

Imagine what happens when developers on their own system start kicking each other out of the development RDP sessions because of their continued behavior that caused them to be thrown out of the actual QA platform in the first place. Add to this the fact that in many regions, (unproductive) developer time is very - I say, very - expensive.

The logic goes a long way: each QVS system (PROD and QA) suddenly starts a fight for resources with QDS. So you split them off. In the end you have 5 or more systems where 2 with a decent amount of cores, RAM and common sense should be sufficient.

It think operating a QlikView Enterprise solution should be a balanced.act: 1. proper configuration, 2. continued platform monitoring and management and 3. discipline. Without the latter in the form of a set of sound rules, every architecture will lead to a complete lock-up sooner or later. And as you said before in another comparable discussion on the same subject, Janaki: you can't keep adding RAM, CPU's or entire systems to the setup forever. At least not without decent scaling & sizing arguments.

One final tip: try to eliminate everything that is unpredictable. The cost of adding a QlikView document or developer should be known before they arrive on the scene. It will make it easier for you to plan (and budget) the growth of your QlikView environment.

Some background information for this post can be found here:

http://community.qlik.com/thread/148298

http://community.qlik.com/thread/148299