You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-8Lines changed: 2 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,5 @@
1
1
# PowerAPI Framework Benchmarks
2
2
3
-
Here’s how the **"What it does"** section could look based on the content you provided:
4
-
5
-
---
6
-
7
3
## What It Does
8
4
9
5
This repository contains the source code for generating and running benchmarks for the **PowerAPI Framework**. These benchmarks are designed to adapt to the configuration and architecture of underlying nodes in the **Grid5000** infrastructure.
@@ -19,9 +15,6 @@ This repository contains the source code for generating and running benchmarks f
19
15
- Upon completion, **rsync** is used to retrieve the results files locally. If the retrieval fails, the job’s state is marked as `UnknownState` for manual review.
20
16
6.**Store Results**: Once all filtered nodes have completed their benchmark jobs, the benchmarking process concludes, and all result files are stored in the `/results.d` directory.
21
17
22
-
This automated workflow ensures efficient and scalable benchmarking tailored to the dynamic nature of the Grid5000 environment.
23
-
24
-
25
18
## Why it exists.
26
19
27
20
This benchmarks aim at measuring the variability introduced by the PowerAPI framework over the RAPL interface.
@@ -76,7 +69,8 @@ Execute the compiled program:
76
69
```bash
77
70
./target/release/benchmarking
78
71
```
79
-
72
+
73
+
You may stop the execution of the process and start it again later, as long as the "jobs.yaml" file is present so the necessary information can be retrieved.
0 commit comments