Dedicated Server is the dedicated computing resources solution provided by ByteHouse cloud data warehouse. By allocating independent computing nodes (Server) to users, it enables resource isolation, performance assurance, and greater flexibility.

Overview #

Dedicated Server is the core execution unit of ByteHouse cloud data warehouse, responsible for receiving user query requests, performing SQL parsing and optimization, and distributing query tasks to execution nodes.

• SQL parsing and execution: Receives SQL query requests, completes syntax and semantic parsing, and generates execution plans.
• Query scheduling: By combining the query optimizer and execution engine, determines the optimal execution path to achieve efficient queries.

use cases #

In a shared resource architecture, multiple users share the same set of Server computing resources. If a user's query task is too heavy, it may affect the query performance of other users. This “resource contention” problem is particularly evident in large-scale concurrent queries and complex analytical tasks.

Therefore, Dedicated Server is suitable for:

• use cases: High-concurrency point queries, high QPS, large-scale data analysis, Compliance, and similar use cases. Currently supported concurrency capability: 10,000 QPS.
• Suggestion: When your virtual warehouse specification is larger than XL (64 core 256 GiB), we recommend enabling Dedicated Server to obtain stable and reliable query performance.

Scenario examples:

• Scenario 1: Real-time analysis and high-concurrency queries: Business scenarios such as internet, gaming, e-commerce, and advertising require processing high-concurrency queries. The isolation and elastic scaling of Dedicated Server provide users with stable performance assurance.
• Scenario 2: Sensitive data analysis in the financial industry: Financial institutions have high requirements for data security and isolation. Dedicated Server can meet compliance requirements.
• Scenario 3: Enterprise-level big data analysis: Enterprise users need to handle a large number of query analysis tasks during business peak periods. Dedicated Server offers stable performance and elastic scaling capabilities.

Performance metrics #

billing #

• Pricing and billing: The dedicated Server currently supports four specifications and also supports prepaid (recommended) and postpaid billing modes. For details on specifications, pricing, and billing for both modes, please refer to the relevant section in the billing document Dedicated server.

  warning

  Dedicated Server is currently at the "tenant"-"environment" level. For a tenant in a single region and a single environment, only one Dedicated Server cluster needs to be activated. At present, a Dedicated Server cluster only supports purchasing 2 nodes. Horizontal scaling capability will be available soon, so please stay tuned.

• Settlement/renewal, overdue payment, cancellation: The settlement and renewal periods for the dedicated Server are independent from those of the public virtual warehouse, but the logic is similar. For details, please refer to the billing document.

• To activate a dedicated Server simultaneously when first enabling ByteHouse, use a user with the AccountAdmin role to log in and activate the service.
• To activate a dedicated Server separately in the console, use a user with either the AccountAdmin or SystemAdmin role to activate the service.
• For more information about roles and users, please refer to Role management.

To activate a 64-core dedicated Server, submit a ticket or contact the ByteHouse team to obtain Allowlist privilege.

You can activate a dedicated Server simultaneously when first enabling ByteHouse, and users who have already enabled ByteHouse can also activate a dedicated Server separately later.

First time enabling ByteHouse #

Activation path: Go to ByteHouse product home page. When first purchasing ByteHouse Cloud Data Warehouse Edition, you can activate a dedicated Server simultaneously.

• Upon first activation, the system will use the created virtual warehouse as the default write virtual warehouse for the dedicated Server. If multiple virtual warehouses are activated simultaneously, the system will use the first virtual warehouse as the default write virtual warehouse.
• You can purchase the appropriate specification according to business needs. Currently, both pay-as-you-go and monthly subscription billing modes are supported.
• When subsequently creating a dedicated Server, you must simultaneously select the write virtual warehouse that will be bound to the current dedicated Server.

Activate separately in the console #

Prerequisites:
Before separately activating a dedicated Server in the console, confirm that you have set the default write virtual warehouse, as shown in the figure below.

If not yet configured, refer to the following steps for instructions.
Go to Tenant Management > Parameter setting to set the default write virtual warehouse. After this is configured, any dedicated Server individually enabled via the console will be bound to the default write virtual warehouse set here.

Procedure:

1. In the ByteHouse console, click the Tenant Management tab.

2. On the basic information tab, in the Dedicated Server module, click Add now.

3. In the pop-up sidebar, configure parameters such as the payment type and specifications for the dedicated Server.
   When purchasing, select the appropriate specifications according to your business needs. Currently, ByteHouse supports both pay-as-you-go and monthly subscription billing modes.
   

4. After completing the purchase on the interface, the dedicated Server you have enabled will begin initialization, and its status will be "Waiting".
   The entire initialization process takes about 5 minutes. Please wait patiently.
   

5. After the dedicated Server is initialized, its status changes to "Running".

   

   tip

   After activating Dedicated Server, user queries will automatically switch from the virtual warehouse (public Server) to the Dedicated Server.

If the current dedicated Server specifications do not meet your requirements, click the Edit button in the row of the dedicated Server, and configure the specifications in the pop-up sidebar. Currently, only upward expansion is supported.

After creating a dedicated Server, you can view the dedicated Server's monitoring metrics data on the Tenant management > Cloud monitor page.

For details on the currently supported dedicated Server monitoring metrics, as well as guidance on creating monitoring alerts via BytePlus Cloud Monitor, see Alarm.

To unsubscribe from a dedicated Server, go to Tenant Management > basic information > Dedicated Server, then click the Server Delete button.