Merge pull request #571 from vprashar2929/cleanup-cpe

chore: remove CPE benchmark and cleanup related code
sustainable-computing-io · Jan 15, 2025 · bd4c15c · bd4c15c
2 parents 07c1c3e + b210c67
commit bd4c15c
Show file tree

Hide file tree

Showing 14 changed files with 31 additions and 1,702 deletions.
diff --git a/README.md b/README.md
@@ -48,7 +48,6 @@ OPTS="ESTIMATOR SERVER" make deploy
 ## Model Training
 
 - [Use Tekton pipeline](./model_training/tekton/README.md)
-- [Use Bash script with CPE operator](./model_training/cpe_script_instruction.md)
 
 ## Local test
 

diff --git a/contributing.md b/contributing.md
@@ -43,13 +43,6 @@ Learn more details about [model training](./model_training/)
 
 ### Introduce new benchmarks
 
-The new benchmark must be supported by [CPE operator](https://github.com/IBM/cpe-operator) for automation.
-Find [examples](https://github.com/IBM/cpe-operator/tree/main/examples).
-
-### CPE-based (deprecated)
-
-`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).
-
 ### Tekton
 
 Create workload `Task` and provide example `Pipeline` to run.

diff --git a/model_training/README.md b/model_training/README.md
@@ -62,17 +62,11 @@ Please confirm the following requirements:
 
 ### Run benchmark and collect metrics
 
-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).
-
-> 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.
-
 - [Tekton Pipeline Instruction](./tekton/README.md)
 
-- [CPE Operator Instruction](./cpe_script_instruction.md)
-
 ### With manual execution
 
-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
+In addition to the above approach, you can manually run your own benchmarks, then collect, train, and export the models by the entrypoint
 
 [Manual Metric Collection and Training with Entrypoint](./cmd_instruction.md)
 

diff --git a/model_training/cmd_instruction.md b/model_training/cmd_instruction.md
@@ -77,7 +77,7 @@ PUBLISHER= # github account of publisher
 
 ### 3.1. Extracting collect date from benchmark file
 
-The benchmark file is created by CPE operator or by query function from step 1.
+The benchmark file is created query function from step 1.
 
 ```bash
 # export execution

diff --git a/model_training/cpe_benchmark/coremark.yaml b/model_training/cpe_benchmark/coremark.yaml
diff --git a/model_training/cpe_benchmark/parsec.yaml b/model_training/cpe_benchmark/parsec.yaml
diff --git a/model_training/cpe_benchmark/sample.yaml b/model_training/cpe_benchmark/sample.yaml