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 Billing > Virtual Instances.
All Virtual Instances are hosted in us-west-2 region by default. Looking for a different region? Contact us.
Rockset offers the following Virtual Instances:
|Dedicated Instance (Predictable Query Performance. Ideal for Production Apps)||Small||4||32 GiB|
|Shared Instance (Variable Query Performance. Ideal for Development)||c12.shared||Variable||Variable|
Typically, the compute you’ll require will depend on four things:
You can choose a Virtual Instance size that meets your needs.
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.
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.
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.
Yes, a Virtual Instance has a fixed amount of compute resources.
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.