Skip to content
Success

Changes

Summary

  1. TiCDC: Reduce resource allocations in TiCDC test pipelines to optimize (commit: 25b5ab2) (details)
Commit 25b5ab260fd9766cc4af8f2a537f588ae5d6c639 by noreply
TiCDC: Reduce resource allocations in TiCDC test pipelines to optimize cost efficiency (#4086)

## Reduce Resource Allocation for TiCDC Integration Test Pipelines

This PR adjusts the CPU and memory resource allocations across multiple
TiCDC integration test pipelines to optimize resource utilization and
reduce costs. The changes are based on performance analysis and aim to
maintain test reliability while using fewer resources.

### Why?
Recent performance evaluations have shown that the existing resource
allocations for these integration tests are higher than necessary. By
reducing the CPU and memory limits, we can:
- Decrease infrastructure costs associated with running these pipelines
- Improve resource availability for other concurrent jobs
- Maintain the same level of test coverage and reliability
- Align resource allocations with actual requirements observed during
test execution

### Changes Made:
- **Build containers** (`pod-build.yaml` files):
  - Reduced CPU from 12 to 6 cores
  - Reduced memory from 16Gi to 8Gi

- **Test containers** (`pod-test.yaml` and `pod.yaml` files):
- For heavy integration tests: Reduced CPU from 12 to 6 cores and memory
from 32Gi to 16Gi
- For light integration tests: Reduced memory from 16Gi to 8Gi (CPU
already at appropriate levels)

### Affected Pipelines:
1. **Kafka Integration Tests** (both heavy and light variants, current
and next-gen):
   - `pull_cdc_kafka_integration_heavy`
   - `pull_cdc_kafka_integration_heavy_next_gen`
   - `pull_cdc_kafka_integration_light`
   - `pull_cdc_kafka_integration_light_next_gen`

2. **MySQL Integration Tests** (both heavy and light variants, current
and next-gen):
   - `pull_cdc_mysql_integration_heavy`
   - `pull_cdc_mysql_integration_heavy_next_gen`
   - `pull_cdc_mysql_integration_light`
   - `pull_cdc_mysql_integration_light_next_gen`

3. **Pulsar Integration Tests** (light variants, current and next-gen):
   - `pull_cdc_pulsar_integration_light`
   - `pull_cdc_pulsar_integration_light_next_gen`

4. **Storage Integration Tests** (both heavy and light variants, current
and next-gen):
   - `pull_cdc_storage_integration_heavy`
   - `pull_cdc_storage_integration_heavy_next_gen`
   - `pull_cdc_storage_integration_light`
   - `pull_cdc_storage_integration_light_next_gen`

### Impact:
These changes are expected to reduce resource consumption by
approximately 50% for CPU and 50-75% for memory across all affected
pipelines, while maintaining test reliability and coverage. The
adjustments have been validated against recent test runs to ensure they
don't compromise test stability or introduce flakiness.

Signed-off-by: tenfyzhong <tenfy@tenfy.cn>
(commit: 25b5ab2)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_pulsar_integration_light/pod-build.yaml (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_light/pod-test.yaml (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_heavy_next_gen/pod-build.yaml (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_heavy/pod-test.yaml (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_heavy_next_gen/pod-test.yaml (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_light/pod-build.yaml (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_pulsar_integration_light/pod-test.yaml (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_heavy/pod-test.yaml (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_heavy/pod-build.yaml (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_light_next_gen/pod.yaml (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_light_next_gen/pod-test.yaml (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_light/pod-build.yaml (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_light/pod-test.yaml (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_light/pod-build.yaml (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_heavy_next_gen/pod.yaml (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_light_next_gen/pod.yaml (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_heavy/pod-test.yaml (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_light_next_gen/pod-build.yaml (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_heavy/pod-build.yaml (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_heavy_next_gen/pod.yaml (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_pulsar_integration_light_next_gen/pod.yaml (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_light/pod-test.yaml (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_heavy/pod-build.yaml (diff)