Qlik Sense Enterprise on Windows: multi-node deployment

You can configure a Qlik Sense enterprise deployment in a variety of different ways to suit the needs of your organization. For example, you can install Qlik Sense services to run on a single node or on multiple nodes for better performance and scalability. In a small single-node deployment, you deploy all services to a single server, which we do not recommend for larger organizations.

This section provides three examples of Qlik Sense deployments.

The following terms are used in the deployment scenarios:

  • Central node: the central point for managing all nodes in a site.
  • Scheduler or Reload node: reloads apps on a schedule, but does not serve content to users.
  • Consumer node: serves apps to users, but is not used to create, process, or reload data.
  • Development node: allows users to create and reload new apps, but does not serve normal consumer traffic.
  • Proxy node: provides load balancing of user traffic to other nodes but does not contain a Qlik Sense Engine Service (QES).
Note: An alternative to using a proxy node is to have a proxy installed on each consumer node and balance the traffic using a hardware load balancer.

Multi-node deployment examples

The scenarios described here are examples of a small, medium, large, and extra-large Qlik Sense enterprise deployments. Every deployment of Qlik Sense is different and these examples only aim to provide a rough indication of what resources would be appropriate for a given workload. The figures included here are flexible, allowing extra capacity for growth and for handling peaks in demand. They are not intended to set a maximum limit on your deployment.

If you have an attribute significantly higher than any of the figures below (such as more reloads or apps) then contact your Qlik partner and perform a full sizing exercise. For more general scalability and performance information, see Performance.

The following table provides some basic performance information for each type of deployment example:

  Single-node (small) Multi-node (medium) Multi-node (large) Multi-node (extra-large)
Apps 50 100 1000 1000
Active apps per day 25 50 125 125
Total users (from UDC) 500 1000 50000 50000
Concurrent users (equals active users within the same hour) 50 100 500 1000

Average app size (in gigabytes)

 

0.1 0.1 0.1 0.1
Maximum app size (in gigabytes) 1 2 5 5
Content creation (objects per hour) 20 40 50 50
Reloads per hour 10 20 400 400
Note:  These figures are examples that you can use for guidance but may vary depending on how you have configured your Qlik Sense deployment.

Single-node (small)

This example illustrates a small, single-node Qlik Sense production deployment where all services are configured to run on the same server.

Single-node site small

Multi-node (medium)

This example illustrates a typical medium-size, multi-node Qlik Sense production deployment consisting of three nodes:

  • Central node/reload node
  • Two consumer nodes

In this configuration, the repository database (PostgreSQL), and the file share are installed together with other Qlik Sense services on the central node. It has two dedicated consumer nodes.

Multi-node site medium

Multi-node (large)

This example illustrates a typical large, multi-node Qlik Sense production deployment providing the ability to scale up both reloads and user load. This deployment consists of the following nodes:

  • Active central node/reload node
  • Passive central node/reload node
  • Four consumer nodes
  • One developer node

In this configuration example, the repository database (PostgreSQL) and the file share are installed on separate, dedicated servers.

Multi-node site large

The active and passive central nodes must have all services installed. Configure the proxy service on consumer nodes to handle user traffic and on both the active/passive central nodes to handle admin traffic.

Note: Only one central node can be active at any one time, while the other node remains passive. However, the scheduler service is always active regardless of whether the central node is in an active or passive state.

Multi-node (extra large)

This example illustrates an extra large, multi-node Qlik Sense production deployment consisting of seven consumer nodes, providing the ability to scale up both reloads and user load. Two nodes are dedicated to large-size apps, three are dedicated to medium-size apps, and two are dedicated to small-size apps. Each consumer node can be configured with security and custom load balancing rules to restrict the size of the apps they can serve.

However, to ensure that the system can still cope with the load you can pre-load some apps in memory. For example, you could pre-load all medium and large sized apps, ensuring that they can be loaded in less than two seconds, even during peak hours. For more information on pre-loading apps, see App preload - a cache warmer.

Note: With very large deployments, development of applications can be resource intensive. It may therefore be appropriate to have a separate deployment dedicated to app development. If you prefer to keep developer and consumer nodes in the same deployment, ensure the resource limits are suitable for the developer nodes. This includes reload time, hyper cube timeout, and amount of RAM.

This deployment consists of the following nodes:

  • Active central node/reload node
  • Passive central node/reload node
  • Seven consumer nodes
  • Two developer nodes

The active and passive central nodes must have all services installed. Configure the proxy service on consumer nodes to handle user traffic and on both the active/passive central nodes to handle admin traffic.

Note: Only one central node can be active at any one time, while the other node remains passive. However, the scheduler service is always active regardless of whether the central node is in an active or passive state.

Did this information help you?

Thanks for letting us know. Is there anything you'd like to tell us about this topic?

Can you tell us why it did not help you and how we can improve it?