Resource groups cap CPU and IOPS share per tenant or session in a multi-tenant OceanBase cluster. Bind OLTP and batch workloads to different groups so analytical jobs do not starve transactional traffic.

Multi-tenant clusters share OBServer processes. Without isolation, a batch job on tenant A can starve OLTP on tenant B.

Resource groups

Define groups mapping to CPU shares and IOPS limits (syntax per your OceanBase 4.x build):

CREATE RESOURCE GROUP olap_group
  MAX_CPU = 30, MIN_CPU = 10;

CREATE RESOURCE GROUP oltp_group
  MAX_CPU = 70, MIN_CPU = 40;

Bind sessions:

SET RESOURCE_GROUP = 'oltp_group';

Noisy neighbor signals

Watch tenant CPU usage, long-running sessions, and memstore freeze events per tenant in OCP.

Testing

Run analytical extracts concurrently with OLTP load in staging. Compare p99 latency with and without resource groups at the same total CPU.

Sources and further reading