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
ASP.NET benchmark workload profiles support running the workload on both a single system as well as in a client/server topology. This means that the workload supports
9
+
operation on a single system or on 2 distinct systems. The client/server topology is typically used when it is desirable to include a network component in the
10
+
overall performance evaluation. In a client/server topology, one system operates in the 'Client' role running the HTTP load generator (Wrk or Bombardier) while the other
11
+
system operates in the 'Server' role running the ASP.NET Kestrel application.
12
+
The Virtual Client instances running on the client and server systems will synchronize with each other before running the workload. In order to support a client/server topology,
13
+
an environment layout file MUST be supplied to each instance of the Virtual Client on the command line to describe the IP address/location of other Virtual Client instances. An
14
+
environment layout file is not required for the single system topology.
In the environment layout file provided to the Virtual Client, define the role of the client system/VM as "Client" and the role of the server system(s)/VM(s) as "Server".
19
+
The spelling of the roles must be exact. The IP addresses of the systems/VMs must be correct as well. The following example illustrates the
20
+
idea. The name of the client must match the name of the system or the value of the agent ID passed in on the command line.
Runs the ASP.NET TechEmpower JSON serialization benchmark using Wrk. Includes a warm-up pass before the benchmark measurement.
@@ -21,6 +65,9 @@ Supports .NET 9 and .NET 10 via the `ParametersOn` conditional parameter system.
21
65
***Dependencies**
22
66
The dependencies defined in the 'Dependencies' section of the profile itself are required in order to run the workload operations effectively.
23
67
* Internet connection.
68
+
* The IP addresses defined in the environment layout (see above) for the Client and Server systems must be correct.
69
+
* The name of the Client and Server instances defined in the environment layout must match the agent/client IDs supplied on the command line (e.g. --client-id)
70
+
or must match the name of the system as defined by the operating system itself.
24
71
25
72
Additional information on components that exist within the 'Dependencies' section of the profile can be found in the following locations:
@@ -65,6 +116,9 @@ Includes a warm-up pass before the benchmark measurement. Supports .NET 9 and .N
65
116
***Dependencies**
66
117
The dependencies defined in the 'Dependencies' section of the profile itself are required in order to run the workload operations effectively.
67
118
* Internet connection.
119
+
* The IP addresses defined in the environment layout (see above) for the Client and Server systems must be correct.
120
+
* The name of the Client and Server instances defined in the environment layout must match the agent/client IDs supplied on the command line (e.g. --client-id)
121
+
or must match the name of the system as defined by the operating system itself.
68
122
69
123
Additional information on components that exist within the 'Dependencies' section of the profile can be found in the following locations:
The dependencies defined in the 'Dependencies' section of the profile itself are required in order to run the workload operations effectively.
113
171
* Internet connection.
172
+
* The IP addresses defined in the environment layout (see above) for the Client and Server systems must be correct.
173
+
* The name of the Client and Server instances defined in the environment layout must match the agent/client IDs supplied on the command line (e.g. --client-id)
174
+
or must match the name of the system as defined by the operating system itself.
114
175
115
176
Additional information on components that exist within the 'Dependencies' section of the profile can be found in the following locations:
Runs the ASP.NET OrchardCore CMS benchmark using Wrk. The server runs the OrchardCore.Cms.Web application
137
203
and Wrk benchmarks the `/about` endpoint. Includes a warm-up pass before the benchmark measurement.
@@ -148,6 +214,9 @@ and Wrk benchmarks the `/about` endpoint. Includes a warm-up pass before the ben
148
214
***Dependencies**
149
215
The dependencies defined in the 'Dependencies' section of the profile itself are required in order to run the workload operations effectively.
150
216
* Internet connection.
217
+
* The IP addresses defined in the environment layout (see above) for the Client and Server systems must be correct.
218
+
* The name of the Client and Server instances defined in the environment layout must match the agent/client IDs supplied on the command line (e.g. --client-id)
219
+
or must match the name of the system as defined by the operating system itself.
151
220
152
221
Additional information on components that exist within the 'Dependencies' section of the profile can be found in the following locations:
0 commit comments