Virtual Instances

A Virtual Instance is a set of compute resources that are used to serve your queries. It comprises a certain amount of CPU and memory. When you issue a query, it will use the resources of your Virtual Instance to execute. If you pick a larger Virtual Instance, your query can use a larger pool of CPU and memory, which typically results in a reduction in query latency. A larger Virtual Instance can also support higher number of concurrent queries.

You will be asked to choose a Virtual Instance shortly after creating your Rockset account. Your queries from this Virtual Instance can access all or any of your collections in your Rockset account.

You can update your account’s Virtual Instance size at any time in the Rockset Console, under Virtual Instances > Configuration.

All Virtual Instances are hosted in us-west-2 region by default. Looking for a different region? Contact us.

#Choosing a Virtual Instance

Rockset offers the following Virtual Instances:

Compute TypeNamevCPURAM
Dedicated Instance (Predictable Query Performance. Ideal for Production Apps)Small432 GiB
Medium864 GiB
Large16128 GiB
XLarge32256 GiB
2XLarge64512 GiB
4XLarge1281024 GiB
8XLarge2562048 GiB
16XLarge5124096 GiB
Shared Instance (Variable Query Performance. Ideal for Development)c12.sharedVariableVariable

Typically, the compute you’ll require will depend on four things:

  • the size of the data you’re querying (data size)
  • the complexity of your query (query complexity)
  • the number of concurrent queries (query load)
  • the query latency requirement of your application (query latency)

You can choose a Virtual Instance size that meets your needs.


For all Dedicated Instances, you can view associated time series metrics in the Rockset Console, under Virtual Instances > Metrics.

Currently, four metrics are available:

  • number of vCPUs (allocated compute)
  • amount of memory (allocated memory)
  • percentage of CPU utilized by leaf and aggregator nodes (cpu utilization)
  • percentage of memory utilized by leaf and aggregator nodes (memory utilization)

Leaf nodes store and ingest data. Aggregator nodes aggregate data as part of queries before results are returned.

Virtual Instance Metrics


#Is the Shared Virtual Instance suitable for production workloads?

The Shared Virtual Instance is not suitable for production workloads. Accounts in this Virtual Instance share a global resource pool and isolation is not guaranteed. Your data is strictly kept isolated from other accounts but you share CPU and memory resources with other accounts. Sharing resources with other accounts allows you to utilize a lot of resources at a cost-effective price and is a great place to start using Rockset. A noisy neighbor can affect the latency and throughput of your queries. Bursty workloads from accounts may impact your query performance and availability.

The Shared Virtual Instance is usually useful for development and prototyping.

#Will moving to a larger Virtual Instance make my queries faster?

Generally, adding compute by switching to a larger Virtual Instance will make your queries faster. Typically, doubling CPU allocation (e.g., moving from Medium (8 CPUs) to Large (16 CPUs) will increase your query performance by approximately 2x (e.g., reduce query latency from 100ms to 50ms). Note that eventually your queries will not be bound by compute and instead reach the limitations of the underlying infrastructure — at which point adding additional compute will cease to affect latency.

#If I expect my query load to increase significantly, do I need to move to a larger Virtual Instance?

Generally, yes. For example, if you’re running 50 queries-per-sec and add an additional 50 queries-per-second (for 100 queries-per-second total), each query will get a proportionally smaller compute allocation and query latency will increase accordingly (generally proportional to the increase in QPS). In this example, you might notice a query latency increase of approximately 2x. If you want your query latencies to remain the same even when you double your queries-per-second, you should migrate to a Virtual Instance that is 2x larger in size.

For this reason we always recommend stress-testing production workloads before launching your application on Rockset.

#Does a Virtual Instance have a fixed amount of compute resources?

Yes, a Virtual Instance has a fixed amount of compute resources.

#Can I migrate my application from one Virtual Instance to another? Does it encounter downtime?

If you want to migrate your application from one Virtual Instance to another, you do not need to make any changes to your application. Please send an email to Rockset customer support and we will migrate it for you. There is no downtime associated with this migration. We are working on making this a self-service option and very soon you will be able to migrate from one Virtual Instance to another via the Rockset console.

Join us on Slack!
Building on Rockset? Come chat with us!