Skip to content

Commit f13c5e4

Browse files
committed
Tech review go/sweet LP
1 parent 7e271e3 commit f13c5e4

24 files changed

+17
-1674
lines changed

content/learning-paths/servers-and-cloud-computing/go-benchmarking-with-sweet/manual_run_benchstat.md

Lines changed: 8 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,6 @@ weight: 52
66
layout: learningpathall
77
---
88

9-
## Section Overview
10-
119
You've successfully run and downloaded the benchmark results from both your Arm-based and x86-based VMs. In this section, you'll compare them to each other using the benchstat tool.
1210

1311

@@ -27,39 +25,36 @@ The file contains the results of the `markdown` benchmark run on the Arm-based c
2725

2826
To compare the results, you'll use `benchstat` to analyze the two result files you downloaded. Since all the prerequisites are already installed on the `c4` and `c4a` instances, benchstat will be run from one of those instances.
2927

30-
1. **Connect to VM:** As demonstrated in the previous chapter, SSH into the `c4a` instance.
3128

32-
2. **Create working directory:** Make a temporary benchstat directory to hold the results files, and cd into it:
29+
1. **Create working directory:** Make a temporary benchstat directory to hold the results files on either the c4a or c4 isntance, and change directory into it:
3330

3431
```bash
3532
mkdir benchstat_results
3633
cd benchstat_results
3734
```
3835

39-
3. **Upload result files:** Click the `UPLOAD FILE` button in the GCP console, and upload the `c4a.results` AND `c4.results` files you downloaded earlier. (This uploads them to your home directory, not to the current directory.)
36+
2. **Upload result files:** Click the `UPLOAD FILE` button in the GCP console, and upload the `c4a.results` AND `c4.results` files you downloaded earlier. (This uploads them to your home directory, not to the current directory.)
4037

4138
![](images/run_manually/16.png)
4239

43-
4. **Verify upload:** You'll know it worked correctly via the confirmation dialog in your terminal:
40+
3. **Verify upload:** You'll know it worked correctly via the confirmation dialog in your terminal:
4441

4542
![](images/run_manually/17.png)
4643

47-
5. **Move files to working directory:** Move the results files to the `benchstat_results` directory, and confirm their presence:
44+
4. **Move files to working directory:** Move the results files to the `benchstat_results` directory, and confirm their presence:
4845

4946
```bash
5047
mv ~/c4a.results ~/c4.results .
5148
ls -al
5249
```
5350

54-
You should see both files in the benchstat_results directory:
51+
You should see both files in the `benchstat_results` directory:
5552

5653
```bash
57-
# Example output:
58-
c4a-48:~/benchstat_results$ ls
5954
c4.results c4a.results
6055
```
6156

62-
6. **Run benchstat:** Now you can run `benchstat` to compare the two results files:
57+
5. **Run benchstat:** Now you can run `benchstat` to compare the two results files:
6358

6459
```bash
6560
export GOPATH=$HOME/go
@@ -68,7 +63,7 @@ To compare the results, you'll use `benchstat` to analyze the two result files y
6863
benchstat c4a.results c4.results > c4a_vs_c4.txt
6964
```
7065

71-
7. **View comparison results:** Run the `cat` command to view the results:
66+
6. **View comparison results:** Run the `cat` command to view the results:
7267

7368
```bash
7469
cat c4a_vs_c4.txt
@@ -77,8 +72,6 @@ To compare the results, you'll use `benchstat` to analyze the two result files y
7772
You should see output similar to the following:
7873

7974
```output
80-
# Example output:
81-
geremy_cohen_arm_com@c4a-48:~/benchstat_results$ cat c4a_vs_c4.txt
8275
│ c4a.results │ c4.results │
8376
│ sec/op │ sec/op vs base │
8477
MarkdownRenderXHTML-48 143.9m ± 1%
@@ -125,4 +118,4 @@ To compare the results, you'll use `benchstat` to analyze the two result files y
125118

126119
At this point, you can download the `c4a_vs_c4.txt` for further analysis or reporting. You can also run the same or different benchmarks with the same, or different combinations of VMs, and continue comparing results using `benchstat`.
127120

128-
Continuing on to the next section, you will learn how to automate and gain enhanced visuals with sweet and benchstat.
121+
In the next section, you will learn how to automate and gain enhanced visuals with sweet and benchstat.

content/learning-paths/servers-and-cloud-computing/go-benchmarking-with-sweet/refactor1/pytest.ini

Lines changed: 0 additions & 5 deletions
This file was deleted.

content/learning-paths/servers-and-cloud-computing/go-benchmarking-with-sweet/refactor1/requirements.txt

Lines changed: 0 additions & 8 deletions
This file was deleted.

content/learning-paths/servers-and-cloud-computing/go-benchmarking-with-sweet/refactor1/rexec_sweet.py

Lines changed: 0 additions & 27 deletions
This file was deleted.

content/learning-paths/servers-and-cloud-computing/go-benchmarking-with-sweet/refactor1/rexec_sweet/__init__.py

Lines changed: 0 additions & 21 deletions
This file was deleted.

0 commit comments

Comments
 (0)