Important

Helios features are now enabled during weekly update windows and are no longer directly tied to SingleStore engine releases. Refer to the release notes to view the latest features available in your Helios cluster.

RESOURCE_POOLS

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.

cgroup-aware

On SingleStore, clusters run in a managed cloud cluster where each node’s effective CPU capacity is constrained by the cluster-level CPU allocation. Therefore, resource governance enforces pool CPU percentages using the minimum of these limits.

Last modified:

Was this article helpful?