you can run QlikView server components on a virtualized platform but you have to expect the following :
- performance loss compared to a similar physical infrastructure will be at least 10-20%
- physical resources will need to be dedicated to the VM (CPU & RAM)
- disk IO & bandwidth should not be forgotten if loading qvws over 100Mb or more than 100 users (impact on qvw loading time, shared / meta / pgo RW speed
- there are some limitations with virtualisation & windows server NLB, so if you intend to cluster QlikView web servers you might need a physical NLB device (or tweak windows / virtualisation configuration)
I have run a virtualised clustered QlikView production environment for 1300 users without problems during 3 years. In peak we were reaching 50 simultaneous connections. Average response time for selections on a 600Mb qvw was around 1.5 seconds
When we tried to see what it would look like on a physical environment with the same specifications, response time was around 0.5 seconds. We decided that, even if 0.5 was better, 1.5 was good enough compared to the 15 minutes it took to generate a report before QlikView. The price of a virtualized machine was also much cheaper for us at that time (less than half the price of physical)
Hope this helps.
It really depends on you esx, vm / network configuration & QlikView setup / apps but in most cases you should expect at least 10% drop in average response time ... which is not much compared to the cost savings that virtualisation brings.
The Qlik whitepaper on virtualization states that :
Testing done by the QlikTech Scalability Center has shown that the addition of server virtualization generally has a small impact on performance (<5%). However, in some test scenarios, particularly those where the server was under heavy load, the addition of virtualization degraded performance as much as 35%.
I'm now working for Qlik but in my previous company I was in charge of managing the QlikView platform. I'm getting my information from there. One would note that I was leasing my VMs from the company IT, and was thus not able to tweak the ESX & VM config.
PFA this whitepaper.