Skip to content

Commit bd4c15c

Browse files
authored
Merge pull request #571 from vprashar2929/cleanup-cpe
chore: remove CPE benchmark and cleanup related code
2 parents 07c1c3e + b210c67 commit bd4c15c

File tree

14 files changed

+31
-1702
lines changed

14 files changed

+31
-1702
lines changed

README.md

-1
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,6 @@ OPTS="ESTIMATOR SERVER" make deploy
4848
## Model Training
4949

5050
- [Use Tekton pipeline](./model_training/tekton/README.md)
51-
- [Use Bash script with CPE operator](./model_training/cpe_script_instruction.md)
5251

5352
## Local test
5453

contributing.md

-7
Original file line numberDiff line numberDiff line change
@@ -43,13 +43,6 @@ Learn more details about [model training](./model_training/)
4343

4444
### Introduce new benchmarks
4545

46-
The new benchmark must be supported by [CPE operator](https://github.com/IBM/cpe-operator) for automation.
47-
Find [examples](https://github.com/IBM/cpe-operator/tree/main/examples).
48-
49-
### CPE-based (deprecated)
50-
51-
`Benchmark` CR has a dependency on `BenchmarkOperator`. Default `BechmarkOperator` is to support [batch/v1/Job API](https://github.com/IBM/cpe-operator/blob/main/examples/none/cpe_v1_none_operator.yaml).
52-
5346
### Tekton
5447

5548
Create workload `Task` and provide example `Pipeline` to run.

model_training/README.md

+1-7
Original file line numberDiff line numberDiff line change
@@ -62,17 +62,11 @@ Please confirm the following requirements:
6262

6363
### Run benchmark and collect metrics
6464

65-
There are two options to run the benchmark and collect the metrics, [CPE-operator](https://github.com/IBM/cpe-operator) with manual script and [Tekton Pipeline](https://github.com/tektoncd/pipeline).
66-
67-
> The adoption of the CPE operator is slated for deprecation. We are on transitioning to the automation of collection and training processes through the Tekton pipeline. Nevertheless, the CPE operator might still be considered for usage in customized benchmarks requiring performance values per sub-workload within the benchmark suite.
68-
6965
- [Tekton Pipeline Instruction](./tekton/README.md)
7066

71-
- [CPE Operator Instruction](./cpe_script_instruction.md)
72-
7367
### With manual execution
7468

75-
In addition to the above two automation approach, you can manually run your own benchmarks, then collect, train, and export the models by the entrypoint
69+
In addition to the above approach, you can manually run your own benchmarks, then collect, train, and export the models by the entrypoint
7670

7771
[Manual Metric Collection and Training with Entrypoint](./cmd_instruction.md)
7872

model_training/cmd_instruction.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ PUBLISHER= # github account of publisher
7777

7878
### 3.1. Extracting collect date from benchmark file
7979

80-
The benchmark file is created by CPE operator or by query function from step 1.
80+
The benchmark file is created query function from step 1.
8181

8282
```bash
8383
# export execution

model_training/cpe_benchmark/coremark.yaml

-36
This file was deleted.

model_training/cpe_benchmark/parsec.yaml

-41
This file was deleted.

model_training/cpe_benchmark/sample.yaml

-33
This file was deleted.

0 commit comments

Comments
 (0)