SQL Service

Applies toSelf-Managed v2

1 min read

On this page

Maximum Number of Parallel SQL Script Translations

This page covers advanced configuration options for the SQL service. Check out the SQL Development User Guide for more general documentation.

Maximum Number of Parallel SQL Script Translations

When you run a SQL Deployment or launch a preview for a SQL query, the SQL service will translate your SQL query to a {flink} JobGraph. Translating a query to a JobGraph requires JVM memory. Ververica Platform limits the number of parallel JobGraph translations in order to stay within the default memory limits of the gateway container.

If there are many concurrent SQL script translations you may experience translation delays. In order to reduce the time of each translation, you may allow more concurrent translations. Because more concurrent translations require more memory, you will also have to increase the memory configuration of the gateway container.

YAML

1vvp:
2  sqlService:
3    pool:
4      # Number of threads that are available for translations.
5      coreSize: 4
6      # The maximum number of threads that are available for translations.
7      # These will be started on demand if there are load spikes.
8      maxSize: 8
9gateway:
10  resources:
11    limits:
12      memory: 4Gi
13    requests:
14      memory: 4Gi

In the above example, we set coreSize: 4 (default 2) and maxSize: 8 (default 4). We recommend to add 500m of memory for each additional thread, resulting in 4Gi in the above example (default 2Gi).

Was this helpful?

Yes No