Skip to main content Skip to complementary content

Assigning engines to improve application performance

When you open an application, Qlik Cloud automatically selects an engine based on application size, reload memory usage, and available system resources. You can manually assign a larger engine to gain more control or improve performance. Manual assignments use Large application capacity.

Engine types and sizes

Qlik Cloud provides two types of engines: shared and dedicated.

Shared engines

Shared engines can run multiple applications concurrently and the default for smaller or less complex applications. They cannot be assigned manually and do not require Large application capacity.

Example specification:

  • 60 GB RAM

  • Up to 14 CPU cores

Dedicated engines

Dedicated engines run a single application at a time and suited for larger or compute-intensive applications. They require Large application capacity and can be manually assigned.

Example specifications:

Engine specifications
Engine type Memory Up to cores*
Large-40 40 GB 10 cores
Large-60 60 GB 14 cores
Large-80 80 GB

20 cores

Large-120 120 GB

30 cores

Large-160 160 GB

40 cores

Large-200 200 GB

50 cores

* “Up to” means resources are provisioned as needed. Not all CPU cores are used simultaneously for every calculation.

Information noteMemory and CPU specifications may change over time. This information reflects the current setup, but Qlik Cloud may update specifications as the platform evolves.

When to manually assign a larger engine

You may want to override the default engine placement when:

  • Your application has heavy visualizations or complex calculations that require more CPU.

  • Your application size or complexity exceeds the default engine allocation.

  • You want to test and validate performance gains using the built-in evaluation tool.

Manual assignments use Large application capacity, so always balance performance benefits against capacity usage.

Information noteYou cannot assign an application to a smaller engine than the one Qlik Cloud selects automatically.

Manually assigning engines to applications

You can manually assigna specific engine size to an application using the placement API. Manual overrides are available through API calls only, and require Tenant Admin or Analytics Admin permissions.

With the placement API, you can:

  • Assign an engine size to an application

  • Check which engine size is currently assigned

  • Remove an engine size override

For instructions and API details, see Qlik Developer: Pin applications to engine sizes.

Comparing application performance across engine sizes

The application performance evaluation tool in Qlik Cloud helps developers assess application performance during user interaction. It measures how efficiently application objects—such as charts, sheets, and KPIs—are calculated and rendered when the application is opened.

This tool is especially useful if you assign a larger engine to an application and want to verify whether the change improves performance.

What you can do with the evaluation tool

  • Measure how long it takes for specific charts, sheets, or objects to calculate.

  • Compare application performance across engine sizes to see whether assigning a larger engine improves speed and responsiveness.

Information noteThe application performance evaluation tool does not test reload performance. It focuses entirely on application usage.

Running a performance evaluation

You can run an application performance evaluation in several ways:

  • Directly from the activity center

  • As part of a Qlik Automate workflow

  • Via the Qlik Cloud APIs

This makes the tool accessible to developers working interactively as well as to those automating application testing.

For more information, see Application performance evaluation.

Capacity consumption considerations

Manual engine assignments affect how much Large application capacity your application uses. The following rules apply:

  • Capacity used = engine size ÷ 4

    • Example: Assigning a 3 GB application to an 80 GB engine consumes 20 GB of Large application capacity at runtime.

  • Qlik does not reduce usage if the application doesn’t fully use the assigned engine.

  • If the application grows and is later automatically assigned to a larger engine, Qlik updates the capacity usage accordingly.

For more information, see Large application support.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!