Settings and Limits

This page covers the setting and limits placed on your Rockset organization which can be customized either by changing your Virtual Instance type or by contacting Rockset customer support. To view your current account settings and limits, navigate to the Settings tab of the Rockset Console.

Resource Allocations

The following settings are limits placed on your Rockset organization which can change based on your Virtual Instance category.

Note: The Dedicated category includes organizations using any Dedicated Virtual Instance, while the Free, Nano, and Micro categories are Shared Virtual Instances.

To change your Virtual Instance type, navigate to the Virtual Instances tab of the Rockset Console.

Note: Trial organizations have a default ingest limit of 100 GiB for each collection. If you would like to raise this limit for your account, add a payment method or contact Rockset customer support.

Storage Size Limit

This refers to the total amount of data that you can store in Rockset.

Rockset accounts on Dedicated Virtual Instances do not have any data size limits; however, as a convenience to you, an artificial limit of 10 TiB is placed on your account so that any runaway process on your account cannot inundate your account with data that you were not intending to store in Rockset. If you would like to raise this limit for your account, please contact Rockset customer support.

System Settings

The following settings are limits placed on your Rockset organization which may be customized for your specific use case by contacting Rockset customer support.

To change your Virtual Instance type, navigate to the Virtual Instances tab of the Rockset Console.

Peak Streaming Ingest Limit

This refers to the maximum rate at which you can add data into Rockset. It is measured as the number of uncompressed bytes of new data being added to your account per second.

The peak streaming ingest limit is dependent on your Virtual Instance type.

Dedicated Virtual Instances do not have any hard limits on streaming ingest rate; however, your streaming ingest rate will be constrained by the Virtual Instance type that you have provisioned. Larger Dedicated Virtual Instances will have directly proportional lower data latencies due to the additional compute resources working on ingest. For instance, upgrading from a 2XLarge to a 4XLarge Dedicated VI typically doubles your peak streaming ingest rate.

Note: The peak streaming ingest limit does not affect your bulk ingest limit during the
initial bulk ingest mode which occurs immediately following collection creation. For instance, if
you are creating a collection from MongoDB, DynamoDB or S3 and that source already has a large
dataset, Rockset will automatically employ a bulk loading mechanism to index the data that is
pre-existing in that source. This bulk loading process occurs immediately following the creation
of the collection, and is not limited to the peak streaming ingest limit that is explained above.
The bulk ingest rate is hundreds of gigabytes per hour. If you need a higher bulk ingest rate,
please contact Rockset customer support.

After the bulk loading process is completed, Rockset streams new updates made to the source and applies those updates continuously. The peak streaming ingest rate limit described above now applies.

Query Execution Timeout

This refers to the limit on the execution time of any individual query running in your Virtual Instance.

On Dedicated Virtual Instances, Asynchronous Queries are available to queue up queries with custom-defined timeouts of up to 30 minutes.

Query Queue Timeout

This refers to the limit on the queue time of any individual query running in your Virtual Instance. Queries are queued when query requests are received while the concurrent query execution limit is reached. They are then executed in FIFO order once the currently running queries and all prior queued queries are done executing.

On Dedicated Virtual Instances, Asynchronous Queries are available to queue up queries with custom-defined timeouts of up to 30 minutes.

Query Memory Limit

This refers to the total amount of memory that a single query can use. This memory is used for storing transient data that is created by intermediate stages of your query execution.

On Shared Virtual Instances, each individual query has a memory limit of 100 MB which can be used during execution. On Dedicated Virtual Instances, the memory available for your queries are determined by the size of the Virtual Instance. In this case, the memory associated with your Virtual Instance is shared by all concurrent queries in your account (for example, larger Dedicated Instance sizes will have higher memory limits).

Concurrent Queries Limits

The Concurrent Queries Limit (CQL) refers to the queue size for queries, specifically the total number of running queries + total number of queued queries.

The Concurrent Query Execution Limit (CQEL) refers to the maximum number of queries that you can execute concurrently in your account.

For both limits, this includes the queries made directly from the Query Editor tab of the Rockset Console, Rockset API, or Query Lambdas. Most queries run in under a second, so for most users the QPS is much higher than the default limit. This default limit can be increased to provide the maximum number of concurrent queries, while still maintaining an expected SLA. Beyond this limit, additional inbound queries will be queued for processing.