Zilliz Cloud Limits

This page provides information about limits on the Zilliz Cloud platform. You can use the OPS system that Zilliz provides to tune most of the settings mentioned on this page. You can still contact us if you need further help.

Organizations, Projects & Members

The following table lists the limits on the maximum number of organizations and projects allowed for a single user.

Item	Max Number	Remarks
Project	10	Each user can create up to 10 projects in 1 organization.
Organization and Project Member	100	An organization can hold up to 100 organization and project members in total.

Collections

Cluster Plan	Max Number	Remarks
Dedicated cluster	64 per CU, and <= 4096	You can create up to 64 collections per CU used in a dedicated cluster and no more than 4,096 collections in the cluster.

In addition to the limits on the number of collections per cluster, Zilliz Cloud also applies limits on consumed capacity. The following formula shows how Zilliz Cloud calculates the general capacity of a cluster. The consumed capacity should be less than the general capacity available.

General Capacity = 512 x Number of CUs

📘How can I know the general capacity of a cluster?

The general capacity of a cluster indicates the maximum physical resources allocated to the cluster, and it can be determined using the following formula:

<= 512 x Number of CUs

For instance,

• In a cluster of 2 CUs, you can create a maximum of 128 collections with a general capacity of 1,024.

• In a cluster of 12 CUs, you can create a maximum of 768 collections with a general capacity of 6,144.

• In a cluster of 32 CUs or more, you can create a maximum of 4,096 collections with a general capacity of 16,384.

📘How can I know the consumed capacity of a cluster?

The consumed capacity of a cluster indicates the physical resources consumed by the cluster.

For instance, let's assume that you have created 50 collections in a cluster; each of the first 20 collections has 20 partitions, while each of the remaining 30 collections has 10 partition. The consumed capacity of the cluster can be calculated as follows:

20 (collections) x 20 (partitions) + 30 (collections) x 10 (partitions) = 400 + 300 = 700

Based on the above calculation, Zilliz Cloud regards the cluster has a consumed capacity of 700.

Zilliz Cloud also imposed rate limits on collection operations including creating, loading, releasing, and dropping collections. The following rate limit applies to collections in both Serverless and Dedicated clusters.

	Rate Limit
Collection Operation (create, load, release, drop)	5 req/s per cluster

Partitions

Cluster Type	Max Number (Per Collection)	Remarks
Dedicated cluster	1,024	You can create up to 1,024 partitions per collection in a dedicated cluster.

When calculating the consumed and general capacity, refer to the notes in Collections. Additionally, the rate limit for creating partitions is 1 partition/s per cluster.

Fields

Item	Max Number
Fields per collection	64
Vector fields per collection	4

Other limits on fields:

• Null values are not supported by any field types.

• Some fields, such as VarChar or JSON, use more memory than expected and can cause the cluster to become full.

Dimensions

The maximum number of dimensions of a vector field is 32,768.

Operations

This section focuses on the rate limit for common data operations in Zilliz Cloud clusters.

Insert

Each insert request/response should be no greater than 64 MB.

The rate limit that applies varies with the cluster types and the number of CUs in use. The following table lists the rate limits for insert operations.

	Insert Rate Limits
Dedicated cluster 1 CU and 2 CUs	4 MB/s
Dedicated cluster 4 - 8 CUs	6 MB/s
Dedicated cluster 12 - 20 CUs	8 MB/s
Dedicated cluster >= 24 CUs	12 MB/s

When inserting data, include all schema-defined fields. Exclude the primary key if the collection has AutoID enabled.

To make inserted entities immediately retrievable in searches and queries, consider changing the consistency level in the search or query requests to Strong. Read Consistency Level for more.

Upsert

Each upsert request/response should be no greater than 64 MB.

The rate limit that applies varies with the cluster types and the number of CUs in use. The following table lists the rate limits for upsert operations.

	Upsert Rate Limits
Dedicated cluster 1 CU and 2 CUs	4 MB/s
Dedicated cluster 4 - 8 CUs	6 MB/s
Dedicated cluster 12 - 20 CUs	8 MB/s
Dedicated cluster >= 24 CUs	12 MB/s

When upserting data, include all schema-defined fields.

To make upserted entities immediately retrievable in searches and queries, consider changing the consistency level in the search or query requests to Strong. Read Consistency Level for more.

Index

Index types vary with field types. The following table lists the indexable field types and the corresponding index types.

Field Type	Index Type	Metric Type
Vector Field	AUTOINDEX	L2, IP, and COSINE
VarChar Field	TRIE	N/A
Int8/16/32/64	STL_SORT	N/A
Float32/64	STL_SORT	N/A

Flush

The rate limit for flush requests is 0.1 requests per second, imposed at the collection level for specific cluster types. This rate limit applies to:

• Serverless clusters compatible with Milvus 2.4.x or later.

• Dedicated clusters upgraded to the beta version, compatible with Milvus 2.4.x or later.

📘Notes

You are not advised to perform flush operations manually. Zilliz Cloud clusters handle it gracefully for you.

Load

The rate limit for load requests is 5 req/s per cluster.

📘Notes

You do not need to perform the load collection for collections that are already loaded, even if new data is coming into these collections.

Search

Each search request/response should be no greater than 64 MB.

The number of query vectors that each search request carries (usually known as nq) varies with your subscription plan:

• For Free and Serverless clusters, the nq is no greater than 10.

• For Dedicated clusters, the nq is no greater than 16,384.

The number that each search response carries (usually known as topK) varies with your subscription plan:

• For Free and Serverless clusters, the topK is no greater than 1,024 entities in return.

• For Dedicated clusters, the topK is no greater than 16,384 entities in return.

Query

Each query request/response should be no greater than 64 MB.

Each query response carries no more than 16,384 entities in return (usually known as topK).

Delete

Each delete request/response should be no greater than 64 MB.

The rate limit for delete requests is 0.5 MB/s per cluster.

Drop

The rate limit for drop requests is 5 req/s per cluster.

Data import

You can have up to 10 running or pending import jobs in a collection.

Zilliz Cloud also imposes limits on the files to import on the web console.

File Type	Local upload	Sync from S3/GCS/Other OSS
JSON	1 GB	1 GB
Numpy	Not support	The maximum size of the folder is 100 GB and the maximum size of each subdirectory is 15 GB
Parquet	Not support	10 GB

For details, refer to Prepare Source Data.

Backup on Console

Manually created backups are permanently retained.

The maximum retention period for automatically created backups is 30 days.

Restore on Console

You can restore a snapshot in the same region as the original cluster of the snapshot. The target cluster of the restoration should use the same CU type as the original one.

IP Access List

Item	Max Number	Remarks
IP Address (CIDR)	20	You can add up to 20 IP addresses to the allow list.