Qlik Community

Ask a Question

QlikView Administration

Discussion Board for collaboration on QlikView Management.

Announcements
Join us at the Cloud Data and Analytics Tour! REGISTER TODAY
cancel
Showing results for 
Search instead for 
Did you mean: 
davyqliks
Creator III
Creator III

High memory usage on Hyper V (Only)

 Hi all,

We're tryign to migrate QV from a VMware ESXi server to Hyper V.

The old config offered 8gb of RAM for QV to use and it worked well for a small number of concurrent users.

On the hyper V server which has 64Gb avalible the very same document will quickly eat up all avalible memory when the first user opens the document via the browser or desktop client (open in server).  Opening the document directly in the client software doesn't trigger the same memory usage.  RAM isn't dynamcially assigned.  Any ideas?  server os : 2019 QVS version: 12.40.20300.0

Thanks in advance  - David.

Labels (3)
1 Solution

Accepted Solutions
davyqliks
Creator III
Creator III
Author

Thanks Brett,

 

It was down to us runing the latest QV server build.  Downgraded a version or two and all is running well now.  Have submitted a bug report to Qlik via my reseller.

 

Thanks.

View solution in original post

2 Replies
Brett_Bleess
Support (Former)
Support (Former)

About the best I can offer is to have a look at the following link and check the settings on the new server to be sure something is not out of whack there:

https://community.qlik.com/t5/Qlik-Scalability/Quick-tips-8-Server-settings-for-best-performance/gpm...

Regards,
Brett

To help users find verified answers, please do not forget to use the "Accept as Solution" button on any post(s) that helped you resolve your problem or question.
I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.
davyqliks
Creator III
Creator III
Author

Thanks Brett,

 

It was down to us runing the latest QV server build.  Downgraded a version or two and all is running well now.  Have submitted a bug report to Qlik via my reseller.

 

Thanks.

View solution in original post