Sign inTry Free

RESOURCE_POOLS

On this page

This view contains information about resource pools.

For more information about these fields, see CREATE RESOURCE POOL.

Column Name

Description

POOL_NAME

The name of a given resource pool.

MEMORY_PERCENTAGE

The percentage of available memory that the given resource pool is allowed to use.

QUERY_TIMEOUT

The number of seconds after which a resource pool is set to cancel queries.

MAX_CONCURRENCY

The maximum number of concurrent queries that can be run across all aggregators at a time for a given resource pool.

SOFT_CPU_LIMIT_PERCENTAGE

An integer between 1 to 100. CPU usage for users can be limited from 1% - 100% of available processing capacity.

HARD_CPU_LIMIT_PERCENTAGE

An integer between 1 to 100. CPU usage for users can be limited from 1% - 100% of available processing capacity.

MAX_QUEUE_DEPTH

The maximum number of queries that will be queued when MAX_CONCURRENCY is exceeded.

CPU Limit Semantics

For both SOFT_CPU_LIMIT_PERCENTAGE and HARD_CPU_LIMIT_PERCENTAGE, the percentage is applied to the available CPU capacity on each node:

  • On bare‑metal or VM‑based deployments, this capacity is based on the host CPU resources visible to the node.

  • On Kubernetes‑based deployments, resource governance is cgroup‑aware. The effective CPU capacity is the minimum of the host cores and the cgroup CPU limit configured for the container, and pool percentages are enforced relative to this effective capacity.

Last modified: February 4, 2026

Was this article helpful?

On this page

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In