Skip to content

Updated aspnet documentation and updated Blender naming schemes #691

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AlexWFMS merged 3 commits into from
Apr 15, 2026
Merged

Updated aspnet documentation and updated Blender naming schemes #691

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
70e6d3a
Add Blender GPU/CPU performance workload profile
Apr 15, 2026
8afa953
Remove unused GpuModel parameter from Blender performance workload pr…
Apr 15, 2026
bbc2405
Update version to 3.0.18
Apr 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion VERSION
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
3.0.17
3.0.18
19 changes: 0 additions & 19 deletions ...lient.Main/profiles/PERF-BLENDER-AMD.json → ...lient.Main/profiles/PERF-GPU-BLENDER.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,6 @@
"SupportedOperatingSystems": "Windows"
},
"Parameters": {
"GpuModel": "",
"BlenderVersion": "4.2.0",
"Scenes": "monster,junkshop,classroom",
"DeviceTypes": "CPU"
Expand All @@ -24,24 +23,6 @@
}
],
"Dependencies": [
{
"Type": "DependencyPackageInstallation",
"Parameters": {
"Scenario": "InstallAMDGPUDriverPackage",
"BlobContainer": "packages",
"BlobName": "amdgpudriver.zip",
"PackageName": "amdgpudriver",
"Extract": true
}
},
{
"Type": "AMDGPUDriverInstallation",
"Parameters": {
"Scenario": "InstallAMDGPUDriver",
"GpuModel": "$.Parameters.GpuModel",
"PackageName": "amdgpudriver"
}
},
{
"Type": "DependencyPackageInstallation",
"Parameters": {
Expand Down
81 changes: 77 additions & 4 deletions website/docs/workloads/aspnet-benchmarks/aspnet-benchmarks-profiles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,50 @@
The following profiles run customer-representative or benchmarking scenarios using ASP.NET server workloads.

* [Workload Details](./aspnet-benchmarks.md)
* [Client/Server Workloads](../../guides/0020-client-server.md)

## Client/Server Topology Support
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
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
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
system operates in the 'Server' role running the ASP.NET Kestrel application.
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,
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
environment layout file is not required for the single system topology.

* [Environment Layouts](../../guides/0020-client-server.md)

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".
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
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.

``` bash
# Single System (environment layout not required)
./VirtualClient --profile=PERF-WEB-ASPNET-WRK.json --system=Demo --timeout=1440

# Multi-System
# On Client Role System...
./VirtualClient --profile=PERF-WEB-ASPNET-WRK.json --system=Demo --timeout=1440 --client-id=Client01 --layout=/any/path/to/layout.json

# On Server Role System...
./VirtualClient --profile=PERF-WEB-ASPNET-WRK.json --system=Demo --timeout=1440 --client-id=Server01 --layout=/any/path/to/layout.json

# Example contents of the 'layout.json' file:
{
"clients": [
{
"name": "Client01",
"role": "Client",
"ipAddress": "10.1.0.1"
},
{
"name": "Server01",
"role": "Server",
"ipAddress": "10.1.0.2"
}
]
}
```

## PERF-WEB-ASPNET-WRK.json
Runs the ASP.NET TechEmpower JSON serialization benchmark using Wrk. Includes a warm-up pass before the benchmark measurement.
Expand All @@ -21,6 +65,9 @@ Supports .NET 9 and .NET 10 via the `ParametersOn` conditional parameter system.
* **Dependencies**
The dependencies defined in the 'Dependencies' section of the profile itself are required in order to run the workload operations effectively.
* Internet connection.
* The IP addresses defined in the environment layout (see above) for the Client and Server systems must be correct.
* 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)
or must match the name of the system as defined by the operating system itself.

Additional information on components that exist within the 'Dependencies' section of the profile can be found in the following locations:
* [Installing Dependencies](https://microsoft.github.io/VirtualClient/docs/category/dependencies/)
Expand All @@ -40,11 +87,15 @@ Supports .NET 9 and .NET 10 via the `ParametersOn` conditional parameter system.
* **Usage Examples**

```bash
# Run with .NET 9 (default)
# When running on a single system (environment layout not required)
./VirtualClient --profile=PERF-WEB-ASPNET-WRK.json --system=Demo --timeout=1440

# Run with .NET 10
./VirtualClient --profile=PERF-WEB-ASPNET-WRK.json --system=Demo --timeout=1440 --parameters="DotNetVersion=10"

# When running in a client/server environment
./VirtualClient --profile=PERF-WEB-ASPNET-WRK.json --system=Demo --timeout=1440 --client-id=Client01 --layout="/any/path/to/layout.json"
./VirtualClient --profile=PERF-WEB-ASPNET-WRK.json --system=Demo --timeout=1440 --client-id=Server01 --layout="/any/path/to/layout.json"
```

## PERF-WEB-ASPNET-WRK-AFFINITY.json
Expand All @@ -65,6 +116,9 @@ Includes a warm-up pass before the benchmark measurement. Supports .NET 9 and .N
* **Dependencies**
The dependencies defined in the 'Dependencies' section of the profile itself are required in order to run the workload operations effectively.
* Internet connection.
* The IP addresses defined in the environment layout (see above) for the Client and Server systems must be correct.
* 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)
or must match the name of the system as defined by the operating system itself.

Additional information on components that exist within the 'Dependencies' section of the profile can be found in the following locations:
* [Installing Dependencies](https://microsoft.github.io/VirtualClient/docs/category/dependencies/)
Expand All @@ -86,11 +140,15 @@ Includes a warm-up pass before the benchmark measurement. Supports .NET 9 and .N
* **Usage Examples**

```bash
# Run with default affinity and .NET 9
# When running on a single system (environment layout not required)
./VirtualClient --profile=PERF-WEB-ASPNET-WRK-AFFINITY.json --system=Demo --timeout=1440

# Run with .NET 10 and custom core affinity
./VirtualClient --profile=PERF-WEB-ASPNET-WRK-AFFINITY.json --system=Demo --timeout=1440 --parameters="DotNetVersion=10,,,ServerCoreAffinity=0-3,,,ClientCoreAffinity=4-7"

# When running in a client/server environment
./VirtualClient --profile=PERF-WEB-ASPNET-WRK-AFFINITY.json --system=Demo --timeout=1440 --client-id=Client01 --layout="/any/path/to/layout.json"
./VirtualClient --profile=PERF-WEB-ASPNET-WRK-AFFINITY.json --system=Demo --timeout=1440 --client-id=Server01 --layout="/any/path/to/layout.json"
```

## PERF-WEB-ASPNET-BOMBARDIER.json
Expand All @@ -111,6 +169,9 @@ with 256 concurrent connections. Uses .NET 8 SDK.
* **Dependencies**
The dependencies defined in the 'Dependencies' section of the profile itself are required in order to run the workload operations effectively.
* Internet connection.
* The IP addresses defined in the environment layout (see above) for the Client and Server systems must be correct.
* 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)
or must match the name of the system as defined by the operating system itself.

Additional information on components that exist within the 'Dependencies' section of the profile can be found in the following locations:
* [Installing Dependencies](https://microsoft.github.io/VirtualClient/docs/category/dependencies/)
Expand All @@ -129,9 +190,14 @@ with 256 concurrent connections. Uses .NET 8 SDK.
* **Usage Examples**

```bash
# Execute the workload profile
# When running on a single system (environment layout not required)
./VirtualClient --profile=PERF-WEB-ASPNET-BOMBARDIER.json --system=Demo --timeout=1440

# When running in a client/server environment
./VirtualClient --profile=PERF-WEB-ASPNET-BOMBARDIER.json --system=Demo --timeout=1440 --client-id=Client01 --layout="/any/path/to/layout.json"
./VirtualClient --profile=PERF-WEB-ASPNET-BOMBARDIER.json --system=Demo --timeout=1440 --client-id=Server01 --layout="/any/path/to/layout.json"
```

## PERF-WEB-ASPNET-ORCHARD-WRK.json
Runs the ASP.NET OrchardCore CMS benchmark using Wrk. The server runs the OrchardCore.Cms.Web application
and Wrk benchmarks the `/about` endpoint. Includes a warm-up pass before the benchmark measurement.
Expand All @@ -148,6 +214,9 @@ and Wrk benchmarks the `/about` endpoint. Includes a warm-up pass before the ben
* **Dependencies**
The dependencies defined in the 'Dependencies' section of the profile itself are required in order to run the workload operations effectively.
* Internet connection.
* The IP addresses defined in the environment layout (see above) for the Client and Server systems must be correct.
* 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)
or must match the name of the system as defined by the operating system itself.

Additional information on components that exist within the 'Dependencies' section of the profile can be found in the following locations:
* [Installing Dependencies](https://microsoft.github.io/VirtualClient/docs/category/dependencies/)
Expand All @@ -168,6 +237,10 @@ and Wrk benchmarks the `/about` endpoint. Includes a warm-up pass before the ben
* **Usage Examples**

```bash
# Execute the workload profile
# When running on a single system (environment layout not required)
./VirtualClient --profile=PERF-WEB-ASPNET-ORCHARD-WRK.json --system=Demo --timeout=1440

# When running in a client/server environment
./VirtualClient --profile=PERF-WEB-ASPNET-ORCHARD-WRK.json --system=Demo --timeout=1440 --client-id=Client01 --layout="/any/path/to/layout.json"
./VirtualClient --profile=PERF-WEB-ASPNET-ORCHARD-WRK.json --system=Demo --timeout=1440 --client-id=Server01 --layout="/any/path/to/layout.json"
```
Loading