CREATE COMPUTE POOL¶

Syntax¶

CREATE COMPUTE POOL [ IF NOT EXISTS ] <name>
  MIN_NODES = <num>
  MAX_NODES = <num>
  INSTANCE_FAMILY = <instance_family_name>
  [ AUTO_RESUME = { TRUE | FALSE } ]
  [ INITIALLY_SUSPENDED = { TRUE | FALSE } ]
  [ AUTO_SUSPEND_SECS = <num>  ]
  [ COMMENT = '<string_literal>' ]

Required parameters¶

name

String that specifies the identifier (that is, the name) for the compute pool; it must be unique for your account. Quoted names for special characters or case-sensitive names are not supported.

MIN_NODES = num

Specifies the minimum number of nodes for the compute pool. This value must be greater than 0. For more information, see Creating a compute pool.

MAX_NODES = num

Specifies the maximum number of nodes for the compute pool.

INSTANCE_FAMILY = instance_family_name

Identifies the type of machine you want to provision for the nodes in the compute pool. The machine type determines the amount of compute resources in the compute pool and, therefore, the number of credits consumed while the compute pool is running.

The INSTANCE_FAMILY values in the following table can be grouped into 3 categories:

• Generic instance types: Provide a balance of CPU, memory and disk. This does not include GPU. These instance family names start with “CPU”.

• High memory instance types: Similar to generic instance types, but these provide more memory. These instance family names start with “HighMemory”.

• Instance types with GPU attached: These instance family names start with “GPU”.

Consumption Table Mapping	INSTANCE_FAMILY	vCPU	Memory (GiB)	Storage (GiB)	GPU	GPU Memory per GPU (GiB)	Max. Limit	Description
CPU | XS	CPU_X64_XS	2	8	250	n/a	n/a	50	Smallest instance available for Snowpark Containers. Ideal for cost-savings and getting started.
CPU | S	CPU_X64_S	4	16	250	n/a	n/a	50	Ideal for hosting multiple services/jobs while saving cost.
CPU | M	CPU_X64_M	8	32	250	n/a	n/a	20	Ideal for having a full stack application or multiple services
CPU | L	CPU_X64_L	32	128	250	n/a	n/a	20	For applications which need an unusually large number of CPUs, memory and Storage.
High-Memory CPU | S	HIGHMEM_X64_S	8	64	250	n/a	n/a	20	For memory intensive applications.
High-Memory CPU | M	HIGHMEM_X64_M	32	256	250	n/a	n/a	20	For hosting multiple memory intensive applications on a single machine.
High-Memory CPU | L	HIGHMEM_X64_L	128	1024	250	n/a	n/a	20	Largest high-memory machine available for processing large in-memory data.
GPU | S	GPU_NV_S	8	32	250	1 NVIDIA A10G	24	10	Our smallest NVIDIA GPU size available for Snowpark Containers to get started.
GPU | M	GPU_NV_M	48	192	250	4 NVIDIA A10G	24	5	Optimized for intensive GPU usage scenarios like Computer Vision or LLMs/VLMs
GPU | L	GPU_NV_L	96	1152	250	8 NVIDIA A100	40	On request	Largest GPU instance for specialized and advanced GPU cases like LLMs and Clustering etc.

Note the following:

• The consumption table link in the first column heading provides information about the credit consumption rate for the specific INSTANCE_FAMILY.

• The Max. Limit column indicates the maximum number of nodes a Snowflake account can provision for the specific INSTANCE_FAMILY type. Contact your account representative to increase the limit.

Optional parameters¶

AUTO_RESUME = { TRUE | FALSE }

Specifies whether to automatically resume a compute pool when a service or job is submitted to it.

• If AUTO_RESUME is FALSE, you need to explicitly resume the compute pool (using ALTER COMPUTE POOL RESUME) before you can start a service or job on the compute pool.

• If AUTO_RESUME is TRUE, if you start a new service on a suspended compute pool, Snowflake starts the compute pool. Similarly, when you use a service either by invoking a service function or accessing ingress (see Using a service), Snowflake starts the previously suspended compute pool and resumes the service.

Default: TRUE

INITIALLY_SUSPENDED = { TRUE | FALSE }

Specifies whether the compute pool is created initially in the suspended state. If you create a compute pool with INITIALLY_SUSPENDED set to TRUE, Snowflake will not provision any nodes requested for the compute pool at the compute pool creation time. You can start the suspended compute pool using ALTER COMPUTE POOL … RESUME.

Default: FALSE

AUTO_SUSPEND_SECS = num

Number of seconds of inactivity after which you want Snowflake to automatically suspend the compute pool. An inactive compute pool is one in which no services or jobs are currently active on any node in the pool. If auto_suspend_secs is set to 0, Snowflake does not suspend the compute pool automatically.

Default: 3600 seconds

COMMENT = 'string_literal'

Specifies a comment for the compute pool.

Default: No value

Access control requirements¶

A role used to execute this SQL command must have the following privileges at a minimum:

For instructions on creating a custom role with a specified set of privileges, see Creating custom roles.

For general information about roles and privilege grants for performing SQL actions on securable objects, see Overview of Access Control.

Usage notes¶

• Regarding metadata:

  Attention

  Customers should ensure that no personal data (other than for a User object), sensitive data, export-controlled data, or other regulated data is entered as metadata when using the Snowflake service. For more information, see Metadata Fields in Snowflake.

Examples¶

Create a 1-node compute pool. This example command specifies the minimum required parameters:

CREATE COMPUTE POOL tutorial_compute_pool
  MIN_NODES = 1
  MAX_NODES = 1
  INSTANCE_FAMILY = CPU_X64_XS;

The following command specifies the optional AUTO_RESUME parameter:

CREATE COMPUTE POOL tutorial_compute_pool
  MIN_NODES = 1
  MAX_NODES = 1
  INSTANCE_FAMILY = CPU_X64_XS
  AUTO_RESUME = FALSE;