QlikView Desktop Citrix Deployment - Resource Question

[greg-anderson]

We are working on QlikView Desktop deployment via Citrix.  

In the current configuration, we are encountering some performance issues when users open documents from shared folders on the development/QA server.  

Network speed and performance checks out, so I'm looking into resource considerations.

How can I determine and support CPU/RAM requirements for a new Citrix configuration under development, based on our documents' size and complexity?

I've search for hardware requirements and sizing, but everything I find is focused on server sizing.

Thanks!

[Gysbert_Wassenaar]

It all depends on the amount of data in a document, the complexity of the expressions used in chart objects, the amount of objects on a sheet and how many apps one user has open simultaneously. A .qvw is often compressed. When loaded in ram it can take up around 7 times the file size. And then the calculation of the expressions and rendering of the sheet objects also uses ram. The simplest way to find out is just open a document, use it and then see what happens with the resource usage. You can get an indicator if you open the sheet properties window and look at the Objects tab, especially the calculation time and memory consumption columns.

Perhaps this helps:

https://community.qlik.com/t5/Qlik-Design-Blog/Recipe-for-a-Memory-Statistics-analysis/ba-p/1476487

And there's the Document Analyzer that may also yield useful information:

https://qlikviewcookbook.com/recipes/download-info/document-analyzer/

[MichaelRobertshaw]

And an additional consideration is that when licensing QlikView Desktop using "Borrowed CALs" from a QlikView Server, these can only be applied to two MacAddresses per User. We discourage use of Desktop Virtualisation for QlikView Development due to the resource contention (particularly RAM) caused by concurrent users working on large documents. Publish QlikView Desktop to only two of the Citrix Servers in your Citrix Farm otherwise licensing and activating the software may require individual licences and an exception in your contract with Qlik. 

Consumers should use a Browser to interact with the QlikView Server. Resource utilization is centralised on that Server, and the consumers can be on many real or virtual desktops.