Hologres offers five instance types for different data volume, concurrency, and resource isolation requirements.
Overview
Virtual Warehouse covers the broadest range of production scenarios and is the default recommendation. Use the guidance below to choose the right instance type.
Hologres Virtual Warehouse (recommended)
Dedicated computing and storage resources. A single instance supports read/write splitting through virtual warehouses, without requiring separate instances.
Choose this when:
-
Data volumes are in the terabyte (TB) or petabyte (PB) range and you run frequent complex queries.
-
You run high-concurrency online services with millisecond-level responses (over 1,000 QPS).
-
You need workload isolation — for example, separating OLAP queries from real-time writes, or isolating resources across business units.
-
Traffic fluctuates significantly with periodic peaks that require rapid scaling.
For more information, see Hologres Virtual Warehouse.
Hologres Serverless
Shared computing with dedicated storage for high-performance, large-scale, low-frequency data manipulation and queries. No reserved computing capacity required.
Choose this when:
-
You are running development or staging environments.
-
You have low-frequency queries that still require high performance when they run.
-
Workloads fluctuate unpredictably and you cannot reserve dedicated computing in advance.
For more information, see Hologres Serverless.
Hologres General-purpose
Dedicated computing and storage at lower cost for lightweight analytics. Can be upgraded to virtual warehouse instances as requirements grow.
Choose this when:
-
Data volume is less than 1 TB.
-
You run low-frequency ad hoc queries or small- to medium-scale BI reports.
-
You need a cost-effective solution or are trialing non-core services.
-
Concurrency is low — for example, internal data platforms or scheduled batch jobs.
Feature comparison
The following table compares active instance types across five capability dimensions.
|
Feature |
Hologres Virtual Warehouse |
Hologres Serverless |
Hologres General-purpose |
|
Resizing |
Supported |
N/A |
Not supported |
|
Scheduled scaling |
Supported |
N/A |
Not supported |
|
Workload isolation |
Supported |
Supported |
Not supported |
|
Automatic throttling |
Supported |
Supported |
Not supported |
|
Serverless computing |
Supported |
Supported |
Supported |
Legacy offerings (deprecating)
These instance types are scheduled for discontinuation. Migrate to Hologres Virtual Warehouse.
Read-only secondary instance
Dedicated computing and storage that attaches to a general-purpose instance for multi-instance read/write splitting. The primary instance handles writes and data manipulation; the read-only replica handles analytics.
Hologres Read-only Secondary is phasing out. Migrate to Hologres Virtual Warehouse as soon as possible.
Legacy comparison attributes:
|
Feature |
Read-only secondary instance |
|
Resizing |
Not supported |
|
Scheduled scaling |
Not supported |
|
Payload isolation |
Supported |
|
Automatic throttling |
Not supported |
|
Serverless computing |
General-purpose instance: Supported / Read-only secondary instance: Not supported |
Hologres Shared Cluster
Shared computing without storage resources. Does not require reading from or writing to Hologres internal tables.
Previous use cases:
-
Accelerating queries on OSS or MaxCompute data.
-
Running burst queries that exceed reserved instance capacity.
-
Connecting BI tools (Tableau, Quick BI, FineReport) to accelerate lakehouse queries.
For more information, see Hologres Shared Cluster.