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: content/learning-paths/servers-and-cloud-computing/tune-network-workloads-on-bare-metal/1_setup.md
+31-31Lines changed: 31 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,9 +11,9 @@ layout: learningpathall
11
11
12
12
There are numerouse client-server and network-based workloads, and Tomcat is a typical example of such applications, which provide services via HTTP/HTTPS network requests.
13
13
14
-
In this section, you'll set up a benchmark environment using Apache Tomcat and `wrk2` to simulate HTTP load and evaluate performance on an Arm-based bare-metal (**__`Nvidia-Grace`__**).
14
+
In this section, you'll set up a benchmark environment using `Apache Tomcat` and `wrk2` to simulate HTTP load and evaluate performance on an Arm-based bare-metal, such as **__`AWS c8g.metal-48xl`__**.
15
15
16
-
## Set up the Tomcat benchmark server on **Nvidia Grace**
16
+
## Set up the Tomcat benchmark server on **AWS c8g.metal-48xl**
17
17
[Apache Tomcat](https://tomcat.apache.org/) is an open-source Java Servlet container that runs Java web applications, handles HTTP requests, and serves dynamic content. It supports technologies such as Servlet, JSP, and WebSocket.
@@ -11,45 +11,79 @@ To achieve maximum performance, ulimit -n 65535 must be executed on both server
11
11
{{% /notice %}}
12
12
13
13
## Optimal baseline before tuning
14
-
- Baseline on Grace bare-metal (default configuration)
15
-
- Baseline on Grace bare-metal (access logging disabled)
16
-
- Baseline on Grace bare-metal (optimal thread count)
14
+
- Align the IOMMU settings with default Ubuntu
15
+
- Baseline on Arm Neoverse bare-metal (default configuration)
16
+
- Baseline on Arm Neoverse bare-metal (access logging disabled)
17
+
- Baseline on Arm Neoverse bare-metal (optimal thread count)
18
+
19
+
### Align the IOMMU settings with default Ubuntu
20
+
21
+
{{% notice Note %}}
22
+
Due to the customized Ubuntu distribution on AWS, you first need to align the IOMMU settings with default Ubuntu: iommu.strict=1 and iommu.passthrough=0.
23
+
{{% /notice %}}
24
+
25
+
1. Setting IOMMU default status, use a text editor to modify the `grub` file by adding or updating the `GRUB_CMDLINE_LINUX` configuration.
### Baseline on Grace bare-metal (access logging disabled)
103
+
### Baseline on Arm Neoverse bare-metal (access logging disabled)
70
104
To disable the access logging, use a text editor to modify the `server.xml` file by commenting out or removing the **`org.apache.catalina.valves.AccessLogValve`** configuration.
71
105
72
106
The file is at:
73
107
```bash
74
-
vi ~/apache-tomcat-11.0.9/conf/server.xml
108
+
vi ~/apache-tomcat-11.0.10/conf/server.xml
75
109
```
76
110
77
111
The configuratin is at the end of the file, and common out or remove it.
@@ -83,10 +117,10 @@ The configuratin is at the end of the file, and common out or remove it.
83
117
-->
84
118
```
85
119
86
-
1. Use the following command on the Grace bare-metal where `Tomcat` is on
120
+
1. Use the following command on the Arm Neoverse bare-metal where `Tomcat` is on
### Baseline on Grace bare-metal (optimal thread count)
142
+
### Baseline on Arm Neoverse bare-metal (optimal thread count)
109
143
To minimize resource contention between threads and overhead from thread context switching, the number of CPU-intensive threads in Tomcat should be aligned with the number of CPU cores.
110
144
111
145
1. When using `wrk` to perform pressure testing on `Tomcat`:
@@ -115,23 +149,39 @@ top -H -p$(pgrep java)
115
149
116
150
You can see the below information
117
151
```bash
118
-
top - 12:12:45 up 1 day, 7:04, 5 users, load average: 7.22, 3.46, 1.75
0 commit comments