topic Re: VM vs Physical in QlikView

VM vs Physical

Mon, 26 Jan 2026 18:19:17 GMT

Hi All,

I had this question being asked from my management over and over....

How response time will be better from physical than VM for end users using wlikview apps.

Re: VM vs Physical

maxgro — Mon, 14 Apr 2014 17:07:10 GMT

a lot of answers if you can try to search in this forum, just two link...

VM vs Phsical hardware

Re: Phsical Machine vs VM for Qlikview

Re: VM vs Physical

Greg_Williams — Mon, 14 Apr 2014 17:15:59 GMT

Lately, in my experience, I have seen less performance degradation when deploying QlikView on a vm environment, instead of on physical hardware. Depending on configurations (optimizations), using contemporary virtualization software (i.e. not 3 versions prior), and performance tuning the QlikView environment will all contribute to great performance to end users on a vm platform.

Hope this Helps.

~Greg

Re: VM vs Physical

Mon, 14 Apr 2014 17:19:11 GMT

So What Yo uare saying that , staying on VM is not big problem?

Re: VM vs Physical

Greg_Williams — Mon, 14 Apr 2014 17:34:09 GMT

Yes. Another option, you can consider virtualizing specific components, example: QlikView Publisher, Web Service, and place the QlikView Server on dedicated hardware. Virtual deployment of Qlik has seen great performance improvements in the past few years. I strongly and respectfully suggest dedicating a vm instance to QlikView alone...if you need to virtualize...as I have learned, QlikView will cannibalize the RAM and CPU on a machine...in a vm instance where QlikView is installed with another application...this can have undesired performance results.

Hope this Helps.

~Greg

Re: VM vs Physical

StefanBackstrand — Tue, 15 Apr 2014 20:42:55 GMT

It might also be worth pointing out that Qvs is not the only service that is worth considering moving to a separate machine. Publisher, or the Distribution Service, is not seldom another reason for resource congestion. When a reload task is run, QDS will spawn a QVB process, which in all intents and purposes is a QlikView core (Qv, Qvs), which will do the reload. This process, like the Qvs, has the potential to use a lot of resources. It is good to keep this in mind, since Qvs and QDS will fight over resources if they are executing heavily at the same time.

So, a real distributed deployment might have Qvs services on separate machines and QDS on separate as well. You usually refer to this as front-end and back-end, for obvious reasons.