Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
MalcolmCICWF
Creator III
Creator III

Qlikview Access Point Slow on Virtual Machine

We recently have been pushing to migrate everything to virtual machines here at the office. We have migrated our entire Qlikview setup (we are on 12.1 SR6) from a 54GB RAM to a 24GB virtual... No settings have changed, everything else is the same with the environment.

My problem is, ever since the migration, I am getting complaints that pulling up reporting from Access Point and making selections within the reports is much slower than previously... incredibly slow even at times... I do notice sometimes when I am seeing slowness out memory usage is at 85% or sometimes higher. our Working Set  for "High" is set tp 90, so that tells me Qlikview should have access to 90% of the memory leaving 10% for the OS and server operations itself right? So if we are seeing memory at 85% and about that's really 95% of what is available to Qlikview? This would then cause contention issues right?

Idk what else I could provide, but I was hoping somebody here would help us out. I keep being told the server isn't starving for resources... that it is the VM, but the only common factor that has changed is the migration to a VM...

Governance Dashboard says that in 2017 we have 77 Unique Users, we have 5 Max Concurrent Sessions (though I don't think it counts reports still help in memory without users in them), what other info/specs could I provide or does anyone have any insight into VMs and Qlikview??

1 Solution

Accepted Solutions
Chip_Matejowsky
Support
Support

Hi Jeremy,

Ensure that the QVS Events logs are configured for High Verbosity. When you notice the slowdown, check the Events log to see if you have virtual memory warnings. If so, then likely that Windows is paging memory for QlikView. That is something you'll want to avoid, as performance is an order magnitude worse if memory is paging. Have a look at the attached PDF "QVMemoryManagementand CPU" for a good description on how utilizes system resources and give you ammunition you need to get the RAM back up to what it was on the physical servers. Also, need to ensure that RAM in virtual environment is statically allocated to the QlikView instance and not dynamically allocated.

Hope this helps,

Chipp

Principal Technical Support Engineer with Qlik Support
Help users find answers! Don't forget to mark a solution that worked for you!

View solution in original post

5 Replies
vvvvvvizard
Partner - Specialist
Partner - Specialist

from 54 gb ON PHYSICAL to 24gb vm, increase ram back to 54GB

MalcolmCICWF
Creator III
Creator III
Author

So I've argued this and tried to explain how memory intensive Qlikview is, but our systems admin says with a VM we should need as much memory...

jerrysvensson
Partner - Specialist II
Partner - Specialist II

It is not just the amount of memory that affect performance in a VMWare setup.

Have a look at the two PDF documents in this thread : Re: What is the current view on running Production QlikView on VMware and Are There Other Options?&g...

Chip_Matejowsky
Support
Support

Hi Jeremy,

Ensure that the QVS Events logs are configured for High Verbosity. When you notice the slowdown, check the Events log to see if you have virtual memory warnings. If so, then likely that Windows is paging memory for QlikView. That is something you'll want to avoid, as performance is an order magnitude worse if memory is paging. Have a look at the attached PDF "QVMemoryManagementand CPU" for a good description on how utilizes system resources and give you ammunition you need to get the RAM back up to what it was on the physical servers. Also, need to ensure that RAM in virtual environment is statically allocated to the QlikView instance and not dynamically allocated.

Hope this helps,

Chipp

Principal Technical Support Engineer with Qlik Support
Help users find answers! Don't forget to mark a solution that worked for you!
MalcolmCICWF
Creator III
Creator III
Author

Thanks guys I have some things to check into, but thanks for your feedback on your experiences. It has been hard to get our server admin to budge on helping remedy the slowness we have seen. Finally got him to increase our virtual memory up to 32GB