Worker Group / Dedicated Query Compute

Exclusive computing power Worker Group

Reserved dedicated computing resources for critical query tasks

Users can purchase exclusive computing power based on the tenant (workspace) level. After purchase, all query requests for this space will be executed by dedicated query nodes, reducing resource contention and significantly enhancing the query experience for dashboards, logs, metrics, links, RUM, and session playback.

Contact sales to obtain a solution View industry scenarios

Worker Group exclusive query computing power node schematic diagram

Tenant-level exclusive resources

Workspace-level purchases allow query resources to be isolated independently, and core spaces no longer compete with shared resource pools.

Queries are faster and more reliable

Designed for large-scale data analysis and high-concurrency query scenarios, reducing queues and waiting for more stable analysis entry points.

Performance is predictable

Fixed specifications, capability boundaries, and expansion paths are clear, making it easier for platform teams to plan key spatial capacity.

Supports elastic burst

During peak hours, you can temporarily expand more query nodes to handle burst visits, and return to regular resources after peak times.

Why is dedicated computing power needed?

Second-level response to the main market and Kanban

Improves query efficiency for business dashboards, real-time alerts, and troubleshooting large screens.

Massive logs, metrics, and link queries are smoother

Complex queries return faster, enabling more timely business insights and fault diagnosis.

Stable experience remains even during multi-person concurrent analysis

Avoid resource competition and ensure efficient team collaboration.

Data query request

Exclusive computing power Worker Group

Faster returns of results

Determine the usage of exclusive computing power based on business query load

Data sources, query windows, and peak events vary across industries. The following are the selection directions. For actual specifications, it is recommended to evaluate together with workspace query windows, concurrent users, refresh frequency, and peak periods.

Automakers and intelligent connectivity

Vehicle logs, OTA updates, and intelligent cockpit service queries

Automakers simultaneously query vehicle logs, T-Box connections, APP/RUM, link and business events during OTA grayscale, holiday travel guarantees, after-sales quality tracking, and intelligent cockpit fault location. This is suitable for placing core vehicle networking spaces into exclusive computing power, searching daily by model, region, version, and device dimension, with peak window Burst re-evaluation.

Specification recommendations XLarge / 4XLarge evaluation

Burst suggests OTA / Travel Assurance Window Evaluation Burst

Search by model, series, region, version, device number, or VIN combination, with complex field dimensions.
R&D, SRE, quality, after-sales, and operations teams share a core connected car dashboard.
OTA releases, holiday travel guarantees, and centralized troubleshooting can experience short-term spikes in queries.

From core space isolation to large-scale query guarantees

When choosing specifications, prioritize the workspace's query window, field complexity, chart refresh frequency, and concurrent users, rather than just the amount of data.

Large

32 nuclears

Suitable for loads Stable query quality

Concurrent morphology Basic concurrency

Data scale

Concurrent query

Peak elasticity

It is suitable for isolating critical workspaces from shared query resources, providing a stable experience for core dashboards and daily troubleshooting.

Schematic diagram of the Large Worker Group node

Burst mode (Peak elastic scaling)

Users can customize peak period periods, allowing them to temporarily expand more query nodes on top of the existing computing power nodes; After peak times, they return to regular resources to handle short-term concurrency, not replacing long-term specification planning.

Applicable specifications All specifications

Expansion methods Horizontal expansion of existing nodes

Applicable time periods Custom peak periods

Usage recommendations Peak usage does not replace long-term planning

Frequently asked questions

Does exclusive hash power affect the billing of logs, metrics, links, and RUM?

Worker Group is mainly used for query performance enhancement and does not replace usage-based billing for logs, metrics, links, RUM, session playback, and other applications. Fees for data collection, storage, and processing will still be charged according to the corresponding options.

When should you buy Worker Group?

When core Kanban, log retrieval, link analysis, or multi-user concurrent queries affect daily work efficiency, or when critical spaces require a more stable query experience, it is suitable to evaluate exclusive computing power.

How do you decide whether to upgrade the specs or enable Burst?

Long-term stable high load is more suitable for upgrading specifications; Short spikes, active windows, or centralized troubleshooting are better suited to enabling Burst. Both can be used together.

Want to know how Worker Group matches your query load?

Book a demo →

Next steps

Get started > View documentation > View pricing >