Snowpark Container Services: New default values and validation of resource requirements for a service¶

You provide resource requirements for a service in the service specification.

The way in which Snowflake handles services with unspecified resource requirements is changing. In addition, the way in which Snowflake validates specified resource requirements is changing:

Before the change:

• If you do not provide any resource requirements, Snowflake assumes your service will consume negligible resources.

• When you provide resource requirements, Snowflake validates the values against the entire node capacity. Resources consumed by Snowpark Container Services system components are not considered.

After the change:

If resource requirements are not provided the following defaults are applied. Note that resource.requests and resource.limits are relative to the node capacity (vCPU and memory) of the instance family of the associated compute pool.

• If a resource request (cpu, memory, or both) is not provided, Snowflake derives one for you:

  • For cpu, the derived value is either 0.5 or the cpu limit you provided, whichever is smaller.

  • For memory, the derived value is either 0.5 GiB or the memory limit you provided, whichever is smaller.

• If a resource limit (cpu, memory, or both) is not provided, Snowflake defaults the limits to the node capacity for the instance family of the associated compute pool.

• If you do provide resource.limits and they exceed the node capacity, Snowflake will cap the limit to the node capacity.

• Snowflake evaluates these resource requirements independently for cpu and memory.

Note that if it’s theoretically impossible for Snowflake to schedule the service on the given compute pool, CREATE SERVICE will fail. Theoretically impossible assumes the compute pool has the maximum number of allowed nodes and there are no other services running on the compute pool. That is, there is no way Snowflake could allocate the requested resources within the compute pool limits. If it’s theoretically possible, but required resources are in use, then CREATE SERVICE will succeed. Some service instances will report status indicating that the service cannot be scheduled due to insufficient resources until resources become available.

Also, with this BCR the node capacity (vCPU and memory) for each instance type has changed as shown:

Ref: 1648