jandres/GenAIExamples
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity

fix wrong format which break online doc build (#1073)

Browse Source 
Co-authored-by: ZhangJianyu <zhang.jianyu@outlook.com>
This commit is contained in:
Neo Zhang Jianyu
2024-11-05 17:01:40 +08:00
committed by GitHub
parent a0921f127f
commit 2d9aeb3715
4 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
CodeGen/benchmark/performance/README.md
View File

@@ -55,7 +55,7 @@ sudo systemctl daemon-reload; sudo systemctl restart containerd
Please deploy CodeGen service before benchmarking. Please deploy CodeGen service before benchmarking.
##### Run Benchmark Test #### Run Benchmark Test
Before the benchmark, we can configure the number of test queries and test output directory by: Before the benchmark, we can configure the number of test queries and test output directory by:
@@ -72,6 +72,6 @@ bash benchmark.sh -n <node_count>
The argument `-n` refers to the number of test nodes. The argument `-n` refers to the number of test nodes.
##### 4. Data collection #### Data collection
All the test results will come to this folder `/tmp/benchmark_output` configured by the environment variable `TEST_OUTPUT_DIR` in previous steps. All the test results will come to this folder `/tmp/benchmark_output` configured by the environment variable `TEST_OUTPUT_DIR` in previous steps.

4
CodeTrans/benchmark/performance/README.md
View File

@@ -55,7 +55,7 @@ sudo systemctl daemon-reload; sudo systemctl restart containerd
Please deploy CodeTrans service before benchmarking. Please deploy CodeTrans service before benchmarking.
##### Run Benchmark Test #### Run Benchmark Test
Before the benchmark, we can configure the number of test queries and test output directory by: Before the benchmark, we can configure the number of test queries and test output directory by:
@@ -72,6 +72,6 @@ bash benchmark.sh -n <node_count>
The argument `-n` refers to the number of test nodes. The argument `-n` refers to the number of test nodes.
##### 4. Data collection #### Data collection
All the test results will come to this folder `/tmp/benchmark_output` configured by the environment variable `TEST_OUTPUT_DIR` in previous steps. All the test results will come to this folder `/tmp/benchmark_output` configured by the environment variable `TEST_OUTPUT_DIR` in previous steps.

4
FaqGen/benchmark/performance/README.md
View File

@@ -55,7 +55,7 @@ sudo systemctl daemon-reload; sudo systemctl restart containerd
Please deploy FaqGen service before benchmarking. Please deploy FaqGen service before benchmarking.
##### Run Benchmark Test #### Run Benchmark Test
Before the benchmark, we can configure the number of test queries and test output directory by: Before the benchmark, we can configure the number of test queries and test output directory by:
@@ -72,6 +72,6 @@ bash benchmark.sh -n <node_count>
The argument `-n` refers to the number of test nodes. The argument `-n` refers to the number of test nodes.
##### 4. Data collection #### Data collection
All the test results will come to this folder `/tmp/benchmark_output` configured by the environment variable `TEST_OUTPUT_DIR` in previous steps. All the test results will come to this folder `/tmp/benchmark_output` configured by the environment variable `TEST_OUTPUT_DIR` in previous steps.

4
VisualQnA/benchmark/performance/README.md
View File

@@ -55,7 +55,7 @@ sudo systemctl daemon-reload; sudo systemctl restart containerd
Please deploy VisualQnA service before benchmarking. Please deploy VisualQnA service before benchmarking.
##### Run Benchmark Test #### Run Benchmark Test
Before the benchmark, we can configure the number of test queries and test output directory by: Before the benchmark, we can configure the number of test queries and test output directory by:
@@ -72,6 +72,6 @@ bash benchmark.sh -n <node_count>
The argument `-n` refers to the number of test nodes. The argument `-n` refers to the number of test nodes.
##### 4. Data collection #### Data collection
All the test results will come to this folder `/tmp/benchmark_output` configured by the environment variable `TEST_OUTPUT_DIR` in previous steps. All the test results will come to this folder `/tmp/benchmark_output` configured by the environment variable `TEST_OUTPUT_DIR` in previous steps.