Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
herard_bertrand
Partner - Contributor III
Partner - Contributor III

Hosting QlikView on AWS Server (Which Instance types to recommend ? )

Hi,

has anyone already used an AWS EC2 Server to host an on-premise QlikView Server ?

I'm completely lost in the list of Instance type :

https://aws.amazon.com/fr/ec2/instance-types/

If someone have advices or best practices to help to choose, don't hesitate 🙂

 

Best regards

Labels (1)
1 Solution

Accepted Solutions
Levi_Turner
Employee
Employee

There isn't a single answer to this, but my thoughts:

  • r5 / r5a* series
    • This is a memory heavy instance type ideal for consumption nodes (QVS) or reload nodes where larger apps are being reloaded.
  • m5 / m5a* series
    • This is a balanced VM type. In deployments with more modest apps with high reload concurrency, often the m5 series can work better for back-end nodes (QDS).

Hope that helps

* In the abstract, AMD EPYC chips have better density of cores (aka more cores available) but lower clock speeds compared to Intel's Xeon Scalable series. This surfaces in single threaded heavy operations (e.g. app open events are the common reference here). So in deployments with larger apps, it becomes wiser to prize clock speed vs. # of cores. This # of cores delta between AMD and Intel is mostly neutered in modern cloud platforms where VMs are provisioned based on fix specifications rather bare metal instances.

 

View solution in original post

3 Replies
Chip_Matejowsky
Support
Support

Moving this thread from the Qlik Sense forum to the QlikView forum for greater visibility

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

There isn't a single answer to this, but my thoughts:

  • r5 / r5a* series
    • This is a memory heavy instance type ideal for consumption nodes (QVS) or reload nodes where larger apps are being reloaded.
  • m5 / m5a* series
    • This is a balanced VM type. In deployments with more modest apps with high reload concurrency, often the m5 series can work better for back-end nodes (QDS).

Hope that helps

* In the abstract, AMD EPYC chips have better density of cores (aka more cores available) but lower clock speeds compared to Intel's Xeon Scalable series. This surfaces in single threaded heavy operations (e.g. app open events are the common reference here). So in deployments with larger apps, it becomes wiser to prize clock speed vs. # of cores. This # of cores delta between AMD and Intel is mostly neutered in modern cloud platforms where VMs are provisioned based on fix specifications rather bare metal instances.

 

herard_bertrand
Partner - Contributor III
Partner - Contributor III
Author

Thanks for the reply 👍