diff --git a/README.md b/README.md index b1a1d8081..13da7ee4c 100644 --- a/README.md +++ b/README.md @@ -3,6 +3,7 @@ [![Pull Request Build](https://github.com/microsoft/VirtualClient/actions/workflows/pull-request.yml/badge.svg)](https://github.com/microsoft/VirtualClient/actions/workflows/pull-request.yml) [![Document Build](https://github.com/microsoft/VirtualClient/actions/workflows/deploy-doc.yml/badge.svg?branch=main)](https://github.com/microsoft/VirtualClient/actions/workflows/deploy-doc.yml) [![Document Deployment](https://github.com/microsoft/VirtualClient/actions/workflows/pages/pages-build-deployment/badge.svg)](https://github.com/microsoft/VirtualClient/actions/workflows/pages/pages-build-deployment) +[![NuGet Release Status](https://msazure.visualstudio.com/One/_apis/build/status/OneBranch/CRC-AIR-Workloads/microsoft.VirtualClient?branchName=main)](https://msazure.visualstudio.com/One/_build/latest?definitionId=297462&branchName=main) Virtual Client is a unified workload and system monitoring platform for running customer-representative scenarios on virtual machines or physical hosts/blades in the Azure Cloud. The platform supports a wide range of different industry standard/benchmark workloads used to measuring various aspects of the system under test (e.g. CPU, I/O, network performance, power consumption). It has been an inner-source project in Microsoft for two years and now it is open sourced on GitHub. @@ -20,13 +21,12 @@ The platform additionally provides the ability to capture important performance ## [Supported Workloads](https://microsoft.github.io/VirtualClient/docs/overview/#supported-benchmark-workloads) +--- ## Please bear with us for a second VirtualClient is an MSFT inner source project we are migrating to GitHub. We are still gradually migrating our code and documents. Please be patient if the documents have wrong links. We are actively cleaning those up. -#### About benchmark examples in source -VirtualClient has example benchmark outputs in source, for unit-testing purpose, to make sure our parsers work correctly. -Those runs might or might not be ran on Azure VMs. The results have also been randomly scrubbed. These examples do not represent Azure VM performance. They are in the source purely for unit testing purposes. + ## Telemetry Notice @@ -34,6 +34,13 @@ Data Collection. The software may collect information about you and your use of the software and send it to Microsoft. Microsoft may use this information to provide services and improve our products and services. You may turn off the telemetry as described in the repository. There are also some features in the software that may enable you and Microsoft to collect data from users of your applications. If you use these features, you must comply with applicable law, including providing appropriate notices to users of your applications together with a copy of Microsoft’s privacy statement. Our privacy statement is located at https://go.microsoft.com/fwlink/?LinkID=824704. You can learn more about data collection and use in the help documentation and our privacy statement. Your use of the software operates as your consent to these practices. +#### VirtualClient does not collect your data by default +VirtualClient does not collect any of your benchmark data and upload to Microsoft. When benchmarking at scale, and leveraging VC's telemetry capabilities, users need to explicitly provide a connection string, that points to a user-owned Azure Data Explorer cluster. VirtualClient does host a Azure storage account to host the benchmark binaries or source. The only information VirtualClient team could infer from usage, is the download traces from Azure storage account. + +#### About benchmark examples in source +VirtualClient has example benchmark outputs in source, for unit-testing purpose, to make sure our parsers work correctly. +Those runs might or might not be ran on Azure VMs. The results have also been randomly scrubbed. These examples do not represent Azure VM performance. They are in the source purely for unit testing purposes. + ## Contributing This project welcomes contributions and suggestions. Most contributions require you to agree to a diff --git a/website/docs/overview/design.md b/website/docs/overview/design.md index e21332f5c..93bdde0cb 100644 --- a/website/docs/overview/design.md +++ b/website/docs/overview/design.md @@ -255,8 +255,8 @@ VirtualClient.exe --profile=PERF-CPU-OPENSSL.json --timeout=1440 --experimentId= "message": "OpenSSLExecutor.Execute", "severityLevel": "1", "itemType": "trace", - "operation_Id": "6978d01d-b28d-4f81-8a0e-6296592dad07" - "operation_ParentId": "00000000-0000-0000-0000-000000000000" + "operation_Id": "6978d01d-b28d-4f81-8a0e-6296592dad07", + "operation_ParentId": "00000000-0000-0000-0000-000000000000", "appName": "VirtualClient", "appHost": "virtualmachine01", "sdkVersion": "1.9.0.0", diff --git a/website/docs/overview/faq.md b/website/docs/overview/faq.md index d4dcb1aa0..5f27f0f2e 100644 --- a/website/docs/overview/faq.md +++ b/website/docs/overview/faq.md @@ -16,17 +16,18 @@ is with automation. That's how VC is born. 2. We need your contribution. If you can make improvements into how VirtualClient runs some benchmarks, we would really appreciate your contribution. This will enable everyone else around the globe ## Why you should (or not) use VirtualClient - +1. VC is so much more than just scripts to automate a workload. The expertise that went into automation is more valuable than automation itself. We understand there is so much to learn about every workload and every piece of hardware. VC is positioned to host the collective wisdom of perf engineers from different fields. We studied how to run every benchmark, and the best configurations to use, so that you don't have to spend your time to learn them. +2. VC has the vision to become the united industrial standard of benchmarking and monitoring systems. +3. ### When VirtualClient is probably not a good fit 1. You only need one-off testing with a workload you already understand. You might have some scripts that doesn't need much maintainces. -2. - +2. You are fine tuning for an absolutely best score from one particular workload, for benchmarking competitions. VirtualClient is designed to measure **general experience** +from customers' perspective. ## How is VC used at Azure -1. Quality is top priority for Azure. -2. Azure uses VC to protect the customer from upadtes that will regress the reliability or performance. +Quality is top priority for Azure. Azure uses VC to protect the customer from updates that will regress the reliability or performance. ## Will VC support commercial workloads like SPECcpu, GeekBench? Yes, VC plans to support commercial workloads in the future releases. VirtualClient needs to establish a model to enable the workload automation, without distributing the workloads themselves. diff --git a/website/docs/overview/overview.md b/website/docs/overview/overview.md index a9afb274f..a120b2c23 100644 --- a/website/docs/overview/overview.md +++ b/website/docs/overview/overview.md @@ -1,6 +1,8 @@ --- id: overview sidebar_position: 1 +keywords: [benchmark, automation, workload, monitoring, microsoft, + coremark,hpcg, lapack, openfoam,redis, memcached, specjvm] --- # Overview @@ -9,9 +11,9 @@ The platform supports a wide range of different industry standard/benchmark work The platform additionally provides the ability to capture important performance and reliability measurements from the underlying system. The platform supports all business-critical Azure environments including guest/VM systems, host/blade systems and data center/DC lab systems. The platform additionally supports both x64 and ARM64 compute architectures. -* [Platform Features](../guides/features) -* [Platform Design](../guides/design) -* [Developer Guide](../developing/develop-guide) +* [Platform Features](../overview/features.md) +* [Platform Design](../overview/design.md) +* [Developer Guide](../developing/develop-guide.md) * [Additional Usage Examples](../category/usage-scenarios) ## Team Contacts @@ -27,7 +29,7 @@ VirtualClient handles the installation and execution of various tools. Individua | **Benchmark** | **Specialization** | **Supported Platforms/Architectures** | **License(s)** | |---|---|---|---| -| [7zip](../workloads/compression/Compression.md) | 7zip compression | linux-x64, linux-arm64 | [GNU LGPL](https://www.7-zip.org/faq.html) | +| [7zip](../workloads/compression/7zip.md) | 7zip compression | linux-x64, linux-arm64 | [GNU LGPL](https://www.7-zip.org/faq.html) | | [AspNetBench](../workloads/aspnetbench/AspNetBench.md) | ASP.NET server | linux-x64, linux-arm64, win-x64, win-arm64 | [**ASP.NET**:MIT](https://github.com/dotnet/aspnetcore/blob/main/LICENSE.txt)
[**Bombardier**:MIT](https://github.com/codesenberg/bombardier/blob/master/LICENSE) | | [CoreMark](../workloads/coremark/CoreMark.md) | Generic CPU | linux-x64,linux-arm64 | [Apache+Custom](https://github.com/eembc/coremark/blob/main/LICENSE.md) | | [CPS](../workloads/network/NetworkSuite.md) | Network RoundTripTime | linux-x64, linux-arm64, win-x64, win-arm64 | MSFT developed | @@ -48,13 +50,13 @@ VirtualClient handles the installation and execution of various tools. Individua | [NTttcp](../workloads/network/NetworkSuite.md) | Network bandwidth | linux-x64, linux-arm64, win-x64, win-arm64 | [MIT](https://github.com/microsoft/ntttcp/blob/main/LICENSE) | | [OpenFOAM](../workloads/openfoam/OpenFOAM.md) | Fluidmechanics | linux-x64, linux-arm64 | [Custom](https://github.com/OpenFOAM/OpenFOAM-10/blob/master/COPYING) | | [OpenSSL](../workloads/openssl/OpenSSL.md) | Cryptography | linux-x64, linux-arm64, win-x64 | [Apache-2.0](https://github.com/openssl/openssl/blob/master/LICENSE.txt) | -| [pbzip2](../workloads/compression/Compression.md) | pbzip2 compression | linux-x64, linux-arm64 | [BSD](http://compression.great-site.net/pbzip2/) | +| [pbzip2](../workloads/compression/pbzip2.md) | pbzip2 compression | linux-x64, linux-arm64 | [BSD](http://compression.great-site.net/pbzip2/) | | [Prime95](../workloads/prime95/prime95.md) | Prime number search | linux-x64 | [Custom](https://www.mersenne.org/legal/) | | [Redis](../workloads/redis/Redis.md) | Redis Performance | linux-x64, linux-arm64 | [**Redis**:BSD-3](https://github.com/redis/redis/blob/unstable/COPYING)
[**Memtier**:GPL-2.0](https://github.com/RedisLabs/memtier_benchmark/blob/master/COPYING) | | [SockPerf](../workloads/network/NetworkSuite.md) | Network latency | linux-x64, linux-arm64 | [Custom](https://github.com/Mellanox/sockperf/blob/sockperf_v2/copying) | | [SPECjvm](../workloads/specjvm/SPECjvm.md) | Java Runtime | linux-x64, linux-arm64, win-x64, win-arm64 | [SPEC](https://www.spec.org/spec/docs/SPEC_General_License.pdf) | | [stress-ng](../workloads/stress-ng/StressNg.md) | Fault Tolerance | linux-x64, linux-arm64 | [GPL-2.0](https://github.com/ColinIanKing/stress-ng/blob/master/COPYING) | -| [SuperBench](../workloads/superbenchmark/Superbenchmark.md) | Machine learning | linux-x64 | [MIT](https://github.com/microsoft/superbenchmark/blob/main/LICENSE) | +| [SuperBench](../workloads/superbenchmark/superbenchmark.md) | Machine learning | linux-x64 | [MIT](https://github.com/microsoft/superbenchmark/blob/main/LICENSE) | @@ -75,11 +77,10 @@ VirtualClient is just migrated from MSFT inner-source to GitHub. We are still re ::: ## Current Stable Version(s) -The following section designates the latest stable versions of the Virtual Client. If the version of the Virtual Client is not in this list, then it is NOT recommended -for use anymore. +The following section designates the latest stable versions of the Virtual Client. If the version of the Virtual Client is not in this list, then it is NOT recommended for use anymore. -### Version WIP -Released on ? +### Version 0.0.2 +Released * NuGet Release diff --git a/website/docs/overview/roadmap.md b/website/docs/overview/roadmap.md deleted file mode 100644 index 7dbf765ce..000000000 --- a/website/docs/overview/roadmap.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -id: roadmap -sidebar_position: 10 ---- - -# Roadmap - -## Platform features -1. Run VirtualClient in Docker -2. Publish VC in mainstream package managers (apt,dnf,yum,zypper) - - -## Workloads - -## Monitors - -## Dependencies - -## Feature request? - -Use GitHub Issue diff --git a/website/docs/overview/vision.md b/website/docs/overview/vision.md new file mode 100644 index 000000000..db8089176 --- /dev/null +++ b/website/docs/overview/vision.md @@ -0,0 +1,33 @@ +--- +id: vision +sidebar_position: 10 +--- + +# Vision +- VirtualClient becomes the industrial standard to running benchmarks. +- VirtualClient becomes the knowledge hub for performance engineering. + +1. No one should spend days learning a benchmark just to run once. +2. + +# Roadmap + +## Platform features +1. Run VirtualClient in Docker +2. Publish VC in mainstream package managers (apt,dnf,yum,zypper) + + +## Workloads +1. Commercial workload will come to VirtualClient soon. We will provide a model to release the automation of a workload, with user provided binaries. + + + +## Monitors +1. NvQual + +## Dependencies + + +## Have something you want to see? +Send us a [Feature request](https://github.com/microsoft/VirtualClient/issues/new?assignees=&labels=&template=feature_request.md&title=) + diff --git a/website/docs/workloads/aspnetbench/AspNetBenchMetrics.md b/website/docs/workloads/aspnetbench/AspNetBenchMetrics.md index 42b7880b2..26095d4f9 100644 --- a/website/docs/workloads/aspnetbench/AspNetBenchMetrics.md +++ b/website/docs/workloads/aspnetbench/AspNetBenchMetrics.md @@ -4,9 +4,7 @@ Virtual Client for net impact analysis. [Bombardier output example](https://github.com/codesenberg/bombardier#examples) -### System Metrics -* [Performance Counters](./PerformanceCounterMetrics.md) -* [Power/Temperature Measurements](./PowerMetrics.md) + ### Workload-Specific Metrics The following metrics are captured during the operations of the AspNetBench workload. diff --git a/website/docs/workloads/aspnetbench/AspNetBenchProfiles.md b/website/docs/workloads/aspnetbench/AspNetBenchProfiles.md index 7e38db089..df563dbb7 100644 --- a/website/docs/workloads/aspnetbench/AspNetBenchProfiles.md +++ b/website/docs/workloads/aspnetbench/AspNetBenchProfiles.md @@ -3,8 +3,7 @@ The following profiles run customer-representative or benchmarking scenarios usi * [Workload Details](./AspNetBench.md) * [Workload Profile Metrics](./AspNetBenchMetrics.md) -* [Workload Packages](./DependencyPackages.md) -* [Usage Scenarios/Examples](./UsageScenarios.md) + ----------------------------------------------------------------------- diff --git a/website/docs/workloads/compression/7zip.md b/website/docs/workloads/compression/7zip.md index 0883e6663..bbe5e81ec 100644 --- a/website/docs/workloads/compression/7zip.md +++ b/website/docs/workloads/compression/7zip.md @@ -1,3 +1,6 @@ +--- +id: 7zip +--- # 7zip 7-Zip is a file archiver with a high compression ratio. diff --git a/website/docs/workloads/compression/CompressionMetrics.md b/website/docs/workloads/compression/CompressionMetrics.md index aa6a5549a..dcabc1602 100644 --- a/website/docs/workloads/compression/CompressionMetrics.md +++ b/website/docs/workloads/compression/CompressionMetrics.md @@ -2,9 +2,7 @@ The following document illustrates the type of results that are emitted by the compression/decompression workloads and captured by the Virtual Client for net impact analysis. -### System Metrics -* [Performance Counters](./PerformanceCounterMetrics.md) -* [Power/Temperature Measurements](./PowerMetrics.md) + ### Workload-Specific Metrics The following metrics are emitted by the compression/decompression workloads itself. diff --git a/website/docs/workloads/compression/CompressionProfiles.md b/website/docs/workloads/compression/CompressionProfiles.md index 6f6f923c0..cfdfa3c30 100644 --- a/website/docs/workloads/compression/CompressionProfiles.md +++ b/website/docs/workloads/compression/CompressionProfiles.md @@ -3,8 +3,7 @@ The following profiles run customer-representative or benchmarking scenarios usi * [Workload Details](./Compression.md) * [Workload Profile Metrics](./CompressionMetrics.md) -* [Workload Packages](./DependencyPackages.md) -* [Usage Scenarios/Examples](./UsageScenarios.md) + ----------------------------------------------------------------------- diff --git a/website/docs/workloads/compression/Gzip.md b/website/docs/workloads/compression/Gzip.md index 1f0c77ade..9d2ef5ee1 100644 --- a/website/docs/workloads/compression/Gzip.md +++ b/website/docs/workloads/compression/Gzip.md @@ -1,3 +1,6 @@ +--- +id: gzip +--- # Gzip gzip is a single-file/stream lossless data compression utility, where the resulting compressed file generally has the suffix .gz. diff --git a/website/docs/workloads/compression/Pbzip2.md b/website/docs/workloads/compression/Pbzip2.md index 12a751450..b7a051021 100644 --- a/website/docs/workloads/compression/Pbzip2.md +++ b/website/docs/workloads/compression/Pbzip2.md @@ -1,3 +1,6 @@ +--- +id: pbzip2 +--- # Pbzip2 PBZIP2 is a parallel implementation of the bzip2 block-sorting file compressor that uses pthreads and achieves near-linear speedup on SMP machines. The output of this version is fully compatible with bzip2 v1.0.2 or newer (ie: anything compressed with pbzip2 can be decompressed with bzip2). PBZIP2 should work on any system that has a pthreads compatible C++ compiler (such as gcc). diff --git a/website/docs/workloads/coremark/CoreMarkMetrics.md b/website/docs/workloads/coremark/CoreMarkMetrics.md index 20593f89c..1973142da 100644 --- a/website/docs/workloads/coremark/CoreMarkMetrics.md +++ b/website/docs/workloads/coremark/CoreMarkMetrics.md @@ -2,9 +2,7 @@ The following document illustrates the type of results that are emitted by the CoreMark workload and captured by the Virtual Client for net impact analysis. -### System Metrics -* [Performance Counters](./PerformanceCounterMetrics.md) -* [Power/Temperature Measurements](./PowerMetrics.md) + ### Workload-Specific Metrics The following metrics are emitted by the CoreMark workload itself. diff --git a/website/docs/workloads/deathstarbench/DeathStarBenchMetrics.md b/website/docs/workloads/deathstarbench/DeathStarBenchMetrics.md index 8c01e944a..64490856d 100644 --- a/website/docs/workloads/deathstarbench/DeathStarBenchMetrics.md +++ b/website/docs/workloads/deathstarbench/DeathStarBenchMetrics.md @@ -3,9 +3,7 @@ The following document illustrates the type of results that are emitted by the DeathStarBench workload and captured by the Virtual Client for net impact analysis. -### System Metrics -* [Performance Counters](./PerformanceCounterMetrics.md) -* [Power/Temperature Measurements](./PowerMetrics.md) + ### Workload-Specific Metrics The following metrics are emitted by the DeathStarBench workload itself. diff --git a/website/docs/workloads/deathstarbench/DeathStarBenchProfiles.md b/website/docs/workloads/deathstarbench/DeathStarBenchProfiles.md index 9eac59933..a56e9aca6 100644 --- a/website/docs/workloads/deathstarbench/DeathStarBenchProfiles.md +++ b/website/docs/workloads/deathstarbench/DeathStarBenchProfiles.md @@ -3,8 +3,7 @@ The following profiles run customer-representative or benchmarking scenarios usi * [Workload Details](./DeathStarBench.md) * [Workload Profile Metrics](./DeathStarBenchMetrics.md) -* [Workload Packages](./DependencyPackages.md) -* [Usage Scenarios/Examples](./UsageScenarios.md) + ----------------------------------------------------------------------- diff --git a/website/docs/workloads/diskspd/DiskSpdMetrics.md b/website/docs/workloads/diskspd/DiskSpdMetrics.md index 2b585a914..155d0bd36 100644 --- a/website/docs/workloads/diskspd/DiskSpdMetrics.md +++ b/website/docs/workloads/diskspd/DiskSpdMetrics.md @@ -2,10 +2,6 @@ The following document illustrates the type of results that are emitted by the DiskSpd workload and captured by the Virtual Client for net impact analysis. -### System Metrics -* [Performance Counters](./PerformanceCounterMetrics.md) -* [Power/Temperature Measurements](./PowerMetrics.md) - ### Workload-Specific Metrics The following metrics are emitted by the DiskSpd workload itself. @@ -806,284 +802,4 @@ The following metrics are emitted by the DiskSpd workload itself. | PERF-IO-DISKSPD.json | diskspd_write_4GB_8k_d1_th1_direct | write iops stdev | 7.56 | 240.94 | 48.4877397260274 | milliseconds | | PERF-IO-DISKSPD.json | diskspd_write_4GB_8k_d1_th1_direct | write latency stdev | 0.178 | 6.31 | 0.6880890410958906 | milliseconds | | PERF-IO-DISKSPD.json | diskspd_write_4GB_8k_d1_th1_direct | write throughput | 3.09 | 7.01 | 5.403904109589042 | MiB/sec | -| PERF-IO-DISKSPD.json | diskspd_write_4GB_8k_d1_th1_direct | write total bytes | 1553489920.0 | 3530235904.0 | 2719901106.849315 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_4k_d16_th32 | total bytes | 196391698432.0 | 200543326208.0 | 199574244790.85716 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_4k_d16_th32 | total IO operations | 47947192.0 | 48960773.0 | 48724180.85714286 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_4k_d16_th32 | total throughput | 312.16 | 318.75 | 317.21035714285707 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_4k_d16_th32 | avg. latency | 100.383 | 102.561 | 100.88967857142859 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_4k_d16_th32 | iops stdev | 176.17 | 3262.71 | 1605.8914285714289 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_4k_d16_th32 | latency stdev | 13.804 | 85.555 | 40.20507142857144 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_4k_d16_th32 | read throughput | 312.16 | 318.75 | 317.21035714285707 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_4k_d16_th32 | read iops | 79911.79 | 81601.01 | 81205.84892857143 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_4k_d16_th32 | read total bytes | 196391698432.0 | 200543326208.0 | 199574244790.85716 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_4k_d16_th32 | read avg. latency | 100.383 | 102.561 | 100.88967857142859 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_4k_d16_th32 | read latency stdev | 13.804 | 85.555 | 40.20507142857144 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_4k_d16_th32 | read IO operations | 47947192.0 | 48960773.0 | 48724180.85714286 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_4k_d16_th32 | read iops stdev | 176.17 | 3262.71 | 1605.8914285714289 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_4k_d16_th32 | total iops | 79911.79 | 81601.01 | 81205.84892857143 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_8k_d16_th32 | read iops | 79461.64 | 81603.15 | 81080.76714285715 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_8k_d16_th32 | read throughput | 620.79 | 637.52 | 633.4432142857143 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_8k_d16_th32 | read IO operations | 47676935.0 | 48963791.0 | 48649086.75 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_8k_d16_th32 | read iops stdev | 210.21 | 3524.33 | 1656.5950000000005 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_8k_d16_th32 | read total bytes | 390569451520.0 | 401111375872.0 | 398533318656.0 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_8k_d16_th32 | latency stdev | 12.329 | 94.133 | 44.33275000000001 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_8k_d16_th32 | read latency stdev | 12.329 | 94.133 | 44.33275000000001 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_8k_d16_th32 | iops stdev | 210.21 | 3524.33 | 1656.595 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_8k_d16_th32 | avg. latency | 100.382 | 103.211 | 101.06321428571428 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_8k_d16_th32 | total iops | 79461.64 | 81603.15 | 81080.76714285715 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_8k_d16_th32 | total throughput | 620.79 | 637.52 | 633.4432142857143 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_8k_d16_th32 | total IO operations | 47676935.0 | 48963791.0 | 48649086.75 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_8k_d16_th32 | total bytes | 390569451520.0 | 401111375872.0 | 398533318656.0 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_8k_d16_th32 | read avg. latency | 100.382 | 103.211 | 101.06321428571428 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_12k_d16_th32 | read iops stdev | 259.44 | 2763.82 | 1444.5707142857144 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_12k_d16_th32 | read avg. latency | 100.383 | 102.272 | 101.03892857142857 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_12k_d16_th32 | read latency stdev | 11.068 | 93.473 | 43.53567857142856 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_12k_d16_th32 | total IO operations | 48096849.0 | 48959991.0 | 48657551.96428572 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_12k_d16_th32 | total throughput | 939.39 | 956.25 | 950.3335714285713 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_12k_d16_th32 | total iops | 80161.0 | 81600.21 | 81095.11464285713 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_12k_d16_th32 | avg. latency | 100.383 | 102.272 | 101.03892857142857 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_12k_d16_th32 | iops stdev | 259.44 | 2763.82 | 1444.5707142857144 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_12k_d16_th32 | read iops | 80161.0 | 81600.21 | 81095.11464285713 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_12k_d16_th32 | latency stdev | 11.068 | 93.473 | 43.53567857142856 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_12k_d16_th32 | read total bytes | 591014080512.0 | 601620369408.0 | 597903998537.1428 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_12k_d16_th32 | read IO operations | 48096849.0 | 48959991.0 | 48657551.96428572 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_12k_d16_th32 | total bytes | 591014080512.0 | 601620369408.0 | 597903998537.1428 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_12k_d16_th32 | read throughput | 939.39 | 956.25 | 950.3335714285713 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_16k_d16_th32 | total IO operations | 44728095.0 | 48959293.0 | 48024810.928571429 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_16k_d16_th32 | total bytes | 732825108480.0 | 802149056512.0 | 786838502253.7142 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_16k_d16_th32 | read IO operations | 44728095.0 | 48959293.0 | 48024810.928571429 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_16k_d16_th32 | read total bytes | 732825108480.0 | 802149056512.0 | 786838502253.7142 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_16k_d16_th32 | read latency stdev | 14.108 | 134.869 | 51.34767857142858 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_16k_d16_th32 | latency stdev | 14.108 | 134.869 | 51.34767857142858 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_16k_d16_th32 | iops stdev | 392.99 | 2913.37 | 1628.6167857142858 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_16k_d16_th32 | avg. latency | 100.386 | 110.011 | 102.4302857142857 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_16k_d16_th32 | total iops | 74545.28 | 81597.75 | 80040.31892857142 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_16k_d16_th32 | total throughput | 1164.77 | 1274.96 | 1250.6300000000004 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_16k_d16_th32 | read avg. latency | 100.386 | 110.011 | 102.4302857142857 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_16k_d16_th32 | read throughput | 1164.77 | 1274.96 | 1250.6300000000004 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_16k_d16_th32 | read iops | 74545.28 | 81597.75 | 80040.31892857142 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_16k_d16_th32 | read iops stdev | 392.99 | 2913.37 | 1628.6167857142858 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_1024k_d16_th32 | read IO operations | 939231.0 | 1167485.0 | 1133960.9642857144 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_1024k_d16_th32 | total bytes | 984855085056.0 | 1224196751360.0 | 1189044252086.8572 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_1024k_d16_th32 | total IO operations | 939231.0 | 1167485.0 | 1133960.9642857144 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_1024k_d16_th32 | total throughput | 1565.36 | 1945.81 | 1889.918571428571 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_1024k_d16_th32 | total iops | 1565.36 | 1945.81 | 1889.918571428571 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_1024k_d16_th32 | avg. latency | 4215.022 | 5255.236 | 4362.195785714286 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_1024k_d16_th32 | iops stdev | 9.16 | 59.85 | 34.74964285714285 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_1024k_d16_th32 | latency stdev | 2318.32 | 8023.45 | 5166.735000000001 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_1024k_d16_th32 | read avg. latency | 4215.022 | 5255.236 | 4362.195785714286 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_1024k_d16_th32 | read iops stdev | 9.16 | 59.85 | 34.74964285714285 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_1024k_d16_th32 | read latency stdev | 2318.32 | 8023.45 | 5166.735000000001 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_1024k_d16_th32 | read total bytes | 984855085056.0 | 1224196751360.0 | 1189044252086.8572 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_1024k_d16_th32 | read iops | 1565.36 | 1945.81 | 1889.918571428571 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randread_496G_1024k_d16_th32 | read throughput | 1565.36 | 1945.81 | 1889.918571428571 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_4k_d16_th32 | write iops stdev | 144.56 | 17915.99 | 3626.5959523809526 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_4k_d16_th32 | write avg. latency | 100.383 | 111.659 | 101.96066666666667 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_4k_d16_th32 | write latency stdev | 10.709 | 117.545 | 49.12878571428572 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_4k_d16_th32 | write throughput | 286.71 | 318.75 | 314.06904761904766 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_4k_d16_th32 | write IO operations | 44038761.0 | 48962045.0 | 48241672.309523809 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_4k_d16_th32 | write total bytes | 180382765056.0 | 200548536320.0 | 197597889779.8095 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_4k_d16_th32 | total bytes | 180382765056.0 | 200548536320.0 | 197597889779.8095 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_4k_d16_th32 | write iops | 73397.87 | 81599.63 | 80401.84119047616 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_4k_d16_th32 | total iops | 73397.87 | 81599.63 | 80401.84119047616 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_4k_d16_th32 | latency stdev | 10.709 | 117.545 | 49.12878571428572 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_4k_d16_th32 | iops stdev | 144.56 | 17915.99 | 3626.595952380953 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_4k_d16_th32 | avg. latency | 100.383 | 111.659 | 101.96066666666664 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_4k_d16_th32 | total throughput | 286.71 | 318.75 | 314.06904761904766 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_4k_d16_th32 | total IO operations | 44038761.0 | 48962045.0 | 48241672.309523809 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_8k_d16_th32 | total throughput | 623.35 | 637.51 | 634.3897619047618 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_8k_d16_th32 | write avg. latency | 100.383 | 102.796 | 100.89997619047617 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_8k_d16_th32 | total iops | 79789.42 | 81600.98 | 81202.02261904761 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_8k_d16_th32 | iops stdev | 295.9 | 2786.88 | 1522.1342857142859 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_8k_d16_th32 | avg. latency | 100.383 | 102.796 | 100.89997619047617 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_8k_d16_th32 | latency stdev | 10.593 | 86.046 | 38.29190476190475 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_8k_d16_th32 | write latency stdev | 10.593 | 86.046 | 38.29190476190475 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_8k_d16_th32 | write total bytes | 392186339328.0 | 401094868992.0 | 399129826450.2857 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_8k_d16_th32 | total bytes | 392186339328.0 | 401094868992.0 | 399129826450.2857 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_8k_d16_th32 | write iops stdev | 295.9 | 2786.88 | 1522.1342857142859 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_8k_d16_th32 | write iops | 79789.42 | 81600.98 | 81202.02261904761 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_8k_d16_th32 | write IO operations | 47874309.0 | 48961776.0 | 48721902.64285714 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_8k_d16_th32 | write throughput | 623.35 | 637.51 | 634.3897619047619 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_8k_d16_th32 | total IO operations | 47874309.0 | 48961776.0 | 48721902.64285714 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_12k_d16_th32 | write avg. latency | 100.383 | 102.757 | 100.96546341463415 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_12k_d16_th32 | write IO operations | 47875637.0 | 48963905.0 | 48693070.682926829 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_12k_d16_th32 | write iops | 79792.68 | 81602.66 | 81154.28512195123 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_12k_d16_th32 | iops stdev | 183.92 | 3268.66 | 1464.6292682926829 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_12k_d16_th32 | write throughput | 935.07 | 956.28 | 951.0263414634147 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_12k_d16_th32 | latency stdev | 10.858 | 90.672 | 42.40743902439023 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_12k_d16_th32 | write latency stdev | 10.858 | 90.672 | 42.40743902439023 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_12k_d16_th32 | write iops stdev | 183.92 | 3268.66 | 1464.6292682926829 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_12k_d16_th32 | total bytes | 588295827456.0 | 601668464640.0 | 598340452551.8049 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_12k_d16_th32 | total IO operations | 47875637.0 | 48963905.0 | 48693070.682926829 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_12k_d16_th32 | total throughput | 935.07 | 956.28 | 951.0263414634147 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_12k_d16_th32 | total iops | 79792.68 | 81602.66 | 81154.28512195123 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_12k_d16_th32 | avg. latency | 100.383 | 102.757 | 100.96546341463415 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_12k_d16_th32 | write total bytes | 588295827456.0 | 601668464640.0 | 598340452551.8049 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_16k_d16_th32 | latency stdev | 10.83 | 96.668 | 42.98836585365853 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_16k_d16_th32 | iops stdev | 268.09 | 3479.15 | 1653.1900000000006 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_16k_d16_th32 | avg. latency | 100.383 | 102.866 | 100.99504878048779 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_16k_d16_th32 | total iops | 79709.33 | 81599.61 | 81125.42390243904 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_16k_d16_th32 | total throughput | 1245.46 | 1274.99 | 1267.5853658536585 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_16k_d16_th32 | total IO operations | 47826175.0 | 48959902.0 | 48675805.73170732 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_16k_d16_th32 | total bytes | 783584051200.0 | 802159034368.0 | 797504401108.2927 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_16k_d16_th32 | write latency stdev | 10.83 | 96.668 | 42.98836585365853 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_16k_d16_th32 | write iops stdev | 268.09 | 3479.15 | 1653.1900000000006 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_16k_d16_th32 | write avg. latency | 100.383 | 102.866 | 100.99504878048782 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_16k_d16_th32 | write iops | 79709.33 | 81599.61 | 81125.42390243904 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_16k_d16_th32 | write throughput | 1245.46 | 1274.99 | 1267.5853658536585 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_16k_d16_th32 | write IO operations | 47826175.0 | 48959902.0 | 48675805.73170732 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_16k_d16_th32 | write total bytes | 783584051200.0 | 802159034368.0 | 797504401108.2927 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_1024k_d16_th32 | write latency stdev | 54.768 | 4270.827 | 1279.9115853658535 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_1024k_d16_th32 | write iops stdev | 0.67 | 47.71 | 18.577317073170734 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_1024k_d16_th32 | write avg. latency | 4205.178 | 4267.489 | 4216.393878048781 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_1024k_d16_th32 | write iops | 1945.22 | 1947.28 | 1945.528048780488 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_1024k_d16_th32 | write throughput | 1945.22 | 1947.28 | 1945.528048780488 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_1024k_d16_th32 | write IO operations | 1167136.0 | 1168393.0 | 1167329.5853658538 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_1024k_d16_th32 | write total bytes | 1223830798336.0 | 1225148858368.0 | 1224033787304.5854 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_1024k_d16_th32 | latency stdev | 54.768 | 4270.827 | 1279.9115853658535 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_1024k_d16_th32 | avg. latency | 4205.178 | 4267.489 | 4216.393878048781 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_1024k_d16_th32 | iops stdev | 0.67 | 47.71 | 18.577317073170734 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_1024k_d16_th32 | total iops | 1945.22 | 1947.28 | 1945.528048780488 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_1024k_d16_th32 | total IO operations | 1167136.0 | 1168393.0 | 1167329.5853658538 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_1024k_d16_th32 | total bytes | 1223830798336.0 | 1225148858368.0 | 1224033787304.5854 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_randwrite_496G_1024k_d16_th32 | total throughput | 1945.22 | 1947.28 | 1945.528048780488 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_4k_d16_th32 | total throughput | 314.04 | 318.75 | 317.08535714285719 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_4k_d16_th32 | total IO operations | 48236854.0 | 48961490.0 | 48704805.28571428 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_4k_d16_th32 | total bytes | 197578153984.0 | 200546263040.0 | 199494882450.2857 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_4k_d16_th32 | avg. latency | 100.385 | 101.997 | 100.94385714285714 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_4k_d16_th32 | read iops stdev | 114.51 | 3166.17 | 1699.5210714285718 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_4k_d16_th32 | read avg. latency | 100.385 | 101.997 | 100.94385714285714 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_4k_d16_th32 | read iops | 80394.26 | 81601.01 | 81173.82214285716 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_4k_d16_th32 | read throughput | 314.04 | 318.75 | 317.08535714285719 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_4k_d16_th32 | read IO operations | 48236854.0 | 48961490.0 | 48704805.28571428 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_4k_d16_th32 | read total bytes | 197578153984.0 | 200546263040.0 | 199494882450.2857 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_4k_d16_th32 | read latency stdev | 16.635 | 93.421 | 45.75046428571428 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_4k_d16_th32 | latency stdev | 16.635 | 93.421 | 45.75046428571428 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_4k_d16_th32 | iops stdev | 114.51 | 3166.17 | 1699.5210714285718 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_4k_d16_th32 | total iops | 80394.26 | 81601.01 | 81173.82214285716 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_8k_d16_th32 | read total bytes | 393841229824.0 | 401083777024.0 | 398629713627.4286 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_8k_d16_th32 | read latency stdev | 12.865 | 94.484 | 47.264428571428577 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_8k_d16_th32 | read iops stdev | 198.85 | 3127.29 | 1693.4332142857148 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_8k_d16_th32 | read avg. latency | 100.385 | 102.359 | 101.04207142857145 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_8k_d16_th32 | latency stdev | 12.865 | 94.484 | 47.264428571428577 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_8k_d16_th32 | iops stdev | 198.85 | 3127.29 | 1693.4332142857148 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_8k_d16_th32 | avg. latency | 100.385 | 102.359 | 101.04207142857145 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_8k_d16_th32 | total iops | 80125.79 | 81600.34 | 81100.40642857144 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_8k_d16_th32 | total throughput | 625.98 | 637.5 | 633.5971428571428 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_8k_d16_th32 | total IO operations | 48076322.0 | 48960422.0 | 48660853.71428572 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_8k_d16_th32 | total bytes | 393841229824.0 | 401083777024.0 | 398629713627.4286 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_8k_d16_th32 | read iops | 80125.79 | 81600.34 | 81100.40642857144 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_8k_d16_th32 | read throughput | 625.98 | 637.5 | 633.5971428571428 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_8k_d16_th32 | read IO operations | 48076322.0 | 48960422.0 | 48660853.71428572 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_12k_d16_th32 | total iops | 80318.34 | 81601.59 | 81046.08392857143 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_12k_d16_th32 | read IO operations | 48192232.0 | 48961389.0 | 48628052.21428572 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_12k_d16_th32 | read latency stdev | 12.581 | 93.833 | 46.45417857142858 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_12k_d16_th32 | read iops | 80318.34 | 81601.59 | 81046.08392857143 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_12k_d16_th32 | read throughput | 941.23 | 956.27 | 949.7582142857144 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_12k_d16_th32 | read total bytes | 592186146816.0 | 601637548032.0 | 597541505609.1428 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_12k_d16_th32 | read iops stdev | 237.72 | 3016.41 | 1609.1757142857139 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_12k_d16_th32 | read avg. latency | 100.382 | 102.114 | 101.10592857142857 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_12k_d16_th32 | latency stdev | 12.581 | 93.833 | 46.45417857142858 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_12k_d16_th32 | iops stdev | 237.72 | 3016.41 | 1609.1757142857146 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_12k_d16_th32 | avg. latency | 100.382 | 102.114 | 101.10592857142857 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_12k_d16_th32 | total throughput | 941.23 | 956.27 | 949.7582142857144 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_12k_d16_th32 | total IO operations | 48192232.0 | 48961389.0 | 48628052.21428572 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_12k_d16_th32 | total bytes | 592186146816.0 | 601637548032.0 | 597541505609.1428 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_16k_d16_th32 | read throughput | 1168.94 | 1274.98 | 1255.204642857143 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_16k_d16_th32 | total bytes | 735432589312.0 | 802152398848.0 | 789712298569.1428 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_16k_d16_th32 | iops stdev | 490.37 | 2917.66 | 1774.1810714285717 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_16k_d16_th32 | avg. latency | 100.384 | 109.495 | 102.03817857142858 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_16k_d16_th32 | total iops | 74812.2 | 81598.83 | 80333.06035714287 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_16k_d16_th32 | total throughput | 1168.94 | 1274.98 | 1255.204642857143 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_16k_d16_th32 | total IO operations | 44887243.0 | 48959497.0 | 48200213.53571428 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_16k_d16_th32 | read iops stdev | 490.37 | 2917.66 | 1774.1810714285717 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_16k_d16_th32 | read IO operations | 44887243.0 | 48959497.0 | 48200213.53571428 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_16k_d16_th32 | read avg. latency | 100.384 | 109.495 | 102.03817857142858 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_16k_d16_th32 | read latency stdev | 15.034 | 119.12 | 54.83242857142858 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_16k_d16_th32 | latency stdev | 15.034 | 119.12 | 54.83242857142857 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_16k_d16_th32 | read total bytes | 735432589312.0 | 802152398848.0 | 789712298569.1428 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_16k_d16_th32 | read iops | 74812.2 | 81598.83 | 80333.06035714287 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_1024k_d16_th32 | avg. latency | 4212.823 | 5191.772 | 4361.814 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_1024k_d16_th32 | read iops stdev | 10.49 | 60.14 | 35.651428571428578 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_1024k_d16_th32 | total bytes | 997570117632.0 | 1223776272384.0 | 1189073949257.1428 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_1024k_d16_th32 | total IO operations | 951357.0 | 1167084.0 | 1133989.2857142857 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_1024k_d16_th32 | total throughput | 1585.57 | 1945.07 | 1889.9535714285715 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_1024k_d16_th32 | total iops | 1585.57 | 1945.07 | 1889.9535714285715 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_1024k_d16_th32 | read total bytes | 997570117632.0 | 1223776272384.0 | 1189073949257.1428 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_1024k_d16_th32 | iops stdev | 10.49 | 60.14 | 35.651428571428578 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_1024k_d16_th32 | read latency stdev | 2252.836 | 8963.995 | 5442.4774285714279 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_1024k_d16_th32 | read avg. latency | 4212.823 | 5191.772 | 4361.814 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_1024k_d16_th32 | read iops | 1585.57 | 1945.07 | 1889.9535714285715 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_1024k_d16_th32 | read throughput | 1585.57 | 1945.07 | 1889.9535714285715 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_1024k_d16_th32 | read IO operations | 951357.0 | 1167084.0 | 1133989.2857142857 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_read_496G_1024k_d16_th32 | latency stdev | 2252.836 | 8963.995 | 5442.4774285714279 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_4k_d16_th32 | write IO operations | 47932660.0 | 48960699.0 | 48700545.37837838 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_4k_d16_th32 | total IO operations | 47932660.0 | 48960699.0 | 48700545.37837838 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_4k_d16_th32 | write iops | 79887.9 | 81600.16 | 81166.38864864865 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_4k_d16_th32 | write avg. latency | 100.381 | 102.606 | 100.94405405405407 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_4k_d16_th32 | write iops stdev | 97.23 | 3361.08 | 1522.6527027027028 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_4k_d16_th32 | total bytes | 196332175360.0 | 200543023104.0 | 199477433869.83784 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_4k_d16_th32 | write latency stdev | 10.536 | 92.786 | 39.31605405405405 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_4k_d16_th32 | latency stdev | 10.536 | 92.786 | 39.31605405405405 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_4k_d16_th32 | total throughput | 312.06 | 318.75 | 317.05648648648647 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_4k_d16_th32 | total iops | 79887.9 | 81600.16 | 81166.38864864865 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_4k_d16_th32 | avg. latency | 100.381 | 102.606 | 100.94405405405407 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_4k_d16_th32 | write throughput | 312.06 | 318.75 | 317.05648648648647 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_4k_d16_th32 | iops stdev | 97.23 | 3361.08 | 1522.6527027027028 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_4k_d16_th32 | write total bytes | 196332175360.0 | 200543023104.0 | 199477433869.83784 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_8k_d16_th32 | write throughput | 521.76 | 637.5 | 624.6937142857145 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_8k_d16_th32 | write iops | 66785.0 | 81599.68 | 79960.8217142857 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_8k_d16_th32 | write iops stdev | 363.17 | 2760.57 | 1520.4877142857138 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_8k_d16_th32 | write avg. latency | 100.382 | 122.749 | 102.76645714285714 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_8k_d16_th32 | total throughput | 521.76 | 637.5 | 624.6937142857145 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_8k_d16_th32 | total iops | 66785.0 | 81599.68 | 79960.8217142857 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_8k_d16_th32 | avg. latency | 100.382 | 122.749 | 102.76645714285714 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_8k_d16_th32 | total IO operations | 40071114.0 | 48959975.0 | 47976816.22857143 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_8k_d16_th32 | total bytes | 328262565888.0 | 401080115200.0 | 393026078544.45718 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_8k_d16_th32 | write latency stdev | 10.735 | 104.218 | 41.852171428571427 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_8k_d16_th32 | latency stdev | 10.735 | 104.218 | 41.852171428571427 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_8k_d16_th32 | iops stdev | 363.17 | 2760.57 | 1520.4877142857138 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_8k_d16_th32 | write total bytes | 328262565888.0 | 401080115200.0 | 393026078544.45718 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_8k_d16_th32 | write IO operations | 40071114.0 | 48959975.0 | 47976816.22857143 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_12k_d16_th32 | write latency stdev | 10.416 | 157.872 | 46.10306896551725 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_12k_d16_th32 | write iops stdev | 45.89 | 3209.05 | 1341.1382758620692 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_12k_d16_th32 | write avg. latency | 100.382 | 158.902 | 107.05765517241378 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_12k_d16_th32 | latency stdev | 10.416 | 157.872 | 46.103068965517248 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_12k_d16_th32 | iops stdev | 45.89 | 3209.05 | 1341.1382758620685 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_12k_d16_th32 | avg. latency | 100.382 | 158.902 | 107.05765517241379 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_12k_d16_th32 | total iops | 51553.42 | 81599.37 | 77975.26448275862 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_12k_d16_th32 | total throughput | 604.14 | 956.24 | 913.7717241379312 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_12k_d16_th32 | total IO operations | 30932661.0 | 48960942.0 | 46785541.551724139 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_12k_d16_th32 | total bytes | 380100538368.0 | 601632055296.0 | 574900734587.5862 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_12k_d16_th32 | write iops | 51553.42 | 81599.37 | 77975.26448275862 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_12k_d16_th32 | write throughput | 604.14 | 956.24 | 913.7717241379311 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_12k_d16_th32 | write IO operations | 30932661.0 | 48960942.0 | 46785541.551724139 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_12k_d16_th32 | write total bytes | 380100538368.0 | 601632055296.0 | 574900734587.5862 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_16k_d16_th32 | write throughput | 643.61 | 1274.98 | 1213.7989285714287 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_16k_d16_th32 | total iops | 41190.9 | 81598.98 | 77683.12607142856 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_16k_d16_th32 | total throughput | 643.61 | 1274.98 | 1213.7989285714287 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_16k_d16_th32 | total IO operations | 24715120.0 | 48959067.0 | 46610041.39285714 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_16k_d16_th32 | total bytes | 404932526080.0 | 802145353728.0 | 763658918180.5714 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_16k_d16_th32 | write iops stdev | 239.37 | 5819.85 | 1830.8392857142856 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_16k_d16_th32 | write avg. latency | 100.384 | 198.877 | 108.77739285714289 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_16k_d16_th32 | write iops | 41190.9 | 81598.98 | 77683.12607142856 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_16k_d16_th32 | write latency stdev | 10.79 | 202.573 | 46.068357142857148 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_16k_d16_th32 | latency stdev | 10.79 | 202.573 | 46.068357142857148 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_16k_d16_th32 | write total bytes | 404932526080.0 | 802145353728.0 | 763658918180.5714 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_16k_d16_th32 | avg. latency | 100.384 | 198.877 | 108.77739285714289 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_16k_d16_th32 | write IO operations | 24715120.0 | 48959067.0 | 46610041.39285714 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_16k_d16_th32 | iops stdev | 239.37 | 5819.85 | 1830.8392857142856 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_1024k_d16_th32 | write throughput | 1945.45 | 1945.62 | 1945.5239285714288 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_1024k_d16_th32 | latency stdev | 46.989 | 4046.301 | 1217.612964285714 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_1024k_d16_th32 | iops stdev | 3.12 | 43.72 | 19.039285714285719 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_1024k_d16_th32 | avg. latency | 4210.578 | 4262.929 | 4217.126678571428 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_1024k_d16_th32 | total iops | 1945.45 | 1945.62 | 1945.5239285714288 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_1024k_d16_th32 | total throughput | 1945.45 | 1945.62 | 1945.5239285714288 |MiB/sec | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_1024k_d16_th32 | total IO operations | 1167281.0 | 1167398.0 | 1167329.6785714287 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_1024k_d16_th32 | total bytes | 1223982841856.0 | 1224105525248.0 | 1224033885037.7144 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_1024k_d16_th32 | write iops | 1945.45 | 1945.62 | 1945.5239285714288 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_1024k_d16_th32 | write total bytes | 1223982841856.0 | 1224105525248.0 | 1224033885037.7144 | | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_1024k_d16_th32 | write avg. latency | 4210.578 | 4262.929 | 4217.126678571428 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_1024k_d16_th32 | write iops stdev | 3.12 | 43.72 | 19.039285714285719 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_1024k_d16_th32 | write latency stdev | 46.989 | 4046.301 | 1217.612964285714 |milliseconds | -| PERF-IO-DISKSPD-STRESS.json | diskspd_write_496G_1024k_d16_th32 | write IO operations | 1167281.0 | 1167398.0 | 1167329.6785714287 | | +| PERF-IO-DISKSPD.json | diskspd_write_4GB_8k_d1_th1_direct | write total bytes | 1553489920.0 | 3530235904.0 | 2719901106.849315 | | \ No newline at end of file diff --git a/website/docs/workloads/diskspd/DiskSpdProfiles.md b/website/docs/workloads/diskspd/DiskSpdProfiles.md index 155ec83c3..27c40a3ec 100644 --- a/website/docs/workloads/diskspd/DiskSpdProfiles.md +++ b/website/docs/workloads/diskspd/DiskSpdProfiles.md @@ -3,8 +3,7 @@ The following profiles run customer-representative or benchmarking scenarios usi * [Workload Details](./DiskSpd.md) * [Workload Profile Metrics](./DiskSpdMetrics.md) -* [Workload Packages](./DependencyPackages.md) -* [Usage Scenarios/Examples](./UsageScenarios.md) + ----------------------------------------------------------------------- diff --git a/website/docs/workloads/fio/FIOMetrics.md b/website/docs/workloads/fio/FIOMetrics.md index 522dcb830..6e050f1d4 100644 --- a/website/docs/workloads/fio/FIOMetrics.md +++ b/website/docs/workloads/fio/FIOMetrics.md @@ -2,9 +2,7 @@ The following document illustrates the type of results that are emitted by the FIO workload and captured by the Virtual Client for net impact analysis. -### System Metrics -* [Performance Counters](./PerformanceCounterMetrics.md) -* [Power/Temperature Measurements](./PowerMetrics.md) + ### Workload-Specific Metrics The following metrics are emitted by the FIO workload itself. diff --git a/website/docs/workloads/fio/FIOProfiles.md b/website/docs/workloads/fio/FIOProfiles.md index 4e2ab0dbe..2623347c4 100644 --- a/website/docs/workloads/fio/FIOProfiles.md +++ b/website/docs/workloads/fio/FIOProfiles.md @@ -3,8 +3,7 @@ The following profiles run customer-representative or benchmarking scenarios usi * [Workload Details](./FIO.md) * [Workload Profile Metrics](./FIOMetrics.md) -* [Workload Packages](./DependencyPackages.md) -* [Usage Scenarios/Examples](./UsageScenarios.md) + ----------------------------------------------------------------------- diff --git a/website/docs/workloads/graph500/Graph500Metrics.md b/website/docs/workloads/graph500/Graph500Metrics.md index b2af8f83d..246ea9423 100644 --- a/website/docs/workloads/graph500/Graph500Metrics.md +++ b/website/docs/workloads/graph500/Graph500Metrics.md @@ -2,9 +2,7 @@ The following document illustrates the type of results that are emitted by the Graph500 workload and captured by the Virtual Client for net impact analysis. -### System Metrics -* [Performance Counters](./PerformanceCounterMetrics.md) -* [Power/Temperature Measurements](./PowerMetrics.md) + ### Workload-Specific Metrics The following metrics are emitted by the Graph500 workload itself. diff --git a/website/docs/workloads/graph500/Graph500profiles.md b/website/docs/workloads/graph500/Graph500profiles.md index 308da22d6..70d48c6a6 100644 --- a/website/docs/workloads/graph500/Graph500profiles.md +++ b/website/docs/workloads/graph500/Graph500profiles.md @@ -3,8 +3,7 @@ The following profiles run customer-representative or benchmarking scenarios usi * [Workload Details](./Graph500.md) * [Workload Profile Metrics](./Graph500Metrics.md) -* [Workload Packages](./DependencyPackages.md) -* [Usage Scenarios/Examples](./UsageScenarios.md) + ----------------------------------------------------------------------- diff --git a/website/docs/workloads/hpcg/HpcgMetrics.md b/website/docs/workloads/hpcg/HpcgMetrics.md index 7db2ff79b..2780e9404 100644 --- a/website/docs/workloads/hpcg/HpcgMetrics.md +++ b/website/docs/workloads/hpcg/HpcgMetrics.md @@ -3,10 +3,6 @@ The following document illustrates the type of results that are emitted by the H Virtual Client for net impact analysis. -### System Metrics -* [Performance Counters](./PerformanceCounterMetrics.md) -* [Power/Temperature Measurements](./PowerMetrics.md) - ### Workload-Specific Metrics The following metrics are captured during the operations of the HPCG workload. diff --git a/website/docs/workloads/lapack/LAPACK.md b/website/docs/workloads/lapack/LAPACK.md index caade389d..7f485dbee 100644 --- a/website/docs/workloads/lapack/LAPACK.md +++ b/website/docs/workloads/lapack/LAPACK.md @@ -1,6 +1,5 @@ --- id: lapack -sidebar_position: 1 --- # LAPACK Workload diff --git a/website/docs/workloads/lapack/LAPACKMetrics.md b/website/docs/workloads/lapack/LAPACKMetrics.md index d4534ec46..adae3afdb 100644 --- a/website/docs/workloads/lapack/LAPACKMetrics.md +++ b/website/docs/workloads/lapack/LAPACKMetrics.md @@ -2,9 +2,7 @@ The following document illustrates the type of results that are emitted by the LAPACK workload and captured by the Virtual Client for net impact analysis. -### System Metrics -* [Performance Counters](./PerformanceCounterMetrics.md) -* [Power/Temperature Measurements](./PowerMetrics.md) + ### Workload-Specific Metrics The following metrics are emitted by the LAPACK workload itself. diff --git a/website/docs/workloads/lapack/LAPACKProfiles.md b/website/docs/workloads/lapack/LAPACKProfiles.md index 77315f14a..a6fdb4f8e 100644 --- a/website/docs/workloads/lapack/LAPACKProfiles.md +++ b/website/docs/workloads/lapack/LAPACKProfiles.md @@ -3,8 +3,7 @@ The following profiles run customer-representative or benchmarking scenarios usi * [Workload Details](./LAPACK.md) * [Workload Profile Metrics](./LAPACKMetrics.md) -* [Workload Packages](./DependencyPackages.md) -* [Usage Scenarios/Examples](./UsageScenarios.md) + ----------------------------------------------------------------------- diff --git a/website/docs/workloads/lmbench/LMbenchMetrics.md b/website/docs/workloads/lmbench/LMbenchMetrics.md index d6a44ac48..b25ac22d2 100644 --- a/website/docs/workloads/lmbench/LMbenchMetrics.md +++ b/website/docs/workloads/lmbench/LMbenchMetrics.md @@ -2,9 +2,7 @@ The following document illustrates the type of results that are emitted by the LMbench workload and captured by the Virtual Client for net impact analysis. -### System Metrics -* [Performance Counters](./PerformanceCounterMetrics.md) -* [Power/Temperature Measurements](./PowerMetrics.md) + ### Workload-Specific Metrics The following metrics are emitted by the LMbench workload itself. diff --git a/website/docs/workloads/lmbench/LMbenchProfiles.md b/website/docs/workloads/lmbench/LMbenchProfiles.md index cd4f9de13..f7af44fdf 100644 --- a/website/docs/workloads/lmbench/LMbenchProfiles.md +++ b/website/docs/workloads/lmbench/LMbenchProfiles.md @@ -3,8 +3,7 @@ The following profiles run customer-representative or benchmarking scenarios usi * [Workload Details](./LMbench.md) * [Workload Profile Metrics](./LMbenchMetrics.md) -* [Workload Packages](./DependencyPackages.md) -* [Usage Scenarios/Examples](./UsageScenarios.md) + ----------------------------------------------------------------------- diff --git a/website/docs/workloads/memcached/MemcachedMetrics.md b/website/docs/workloads/memcached/MemcachedMetrics.md index 2e8a99784..5a78272cc 100644 --- a/website/docs/workloads/memcached/MemcachedMetrics.md +++ b/website/docs/workloads/memcached/MemcachedMetrics.md @@ -1,9 +1,7 @@ # Memcached Workload Metrics The following document illustrates the type of results that are emitted by the Memcached workload and captured by the Virtual Client for net impact analysis. -### System Metrics -* [Performance Counters](./PerformanceCounterMetrics.md) -* [Power/Temperature Measurements](./PowerMetrics.md) + ### Workload-Specific Metrics diff --git a/website/docs/workloads/memcached/MemcachedProfiles.md b/website/docs/workloads/memcached/MemcachedProfiles.md index f69445577..4ea362e4e 100644 --- a/website/docs/workloads/memcached/MemcachedProfiles.md +++ b/website/docs/workloads/memcached/MemcachedProfiles.md @@ -3,8 +3,7 @@ The following profiles run customer-representative or benchmarking scenarios usi * [Workload Details](./Memcached.md) * [Workload Profile Metrics](./MemcachedMetrics.md) -* [Workload Packages](./DependencyPackages.md) -* [Usage Scenarios/Examples](./UsageScenarios.md) + ----------------------------------------------------------------------- diff --git a/website/docs/workloads/mlperf/MLPerfMetrics.md b/website/docs/workloads/mlperf/MLPerfMetrics.md index f0ec53e9e..451504558 100644 --- a/website/docs/workloads/mlperf/MLPerfMetrics.md +++ b/website/docs/workloads/mlperf/MLPerfMetrics.md @@ -5,9 +5,7 @@ Virtual Client for net impact analysis. * [MLPerf Training Benchmarks](https://github.com/mlcommons/training_results_v2.0/tree/main/NVIDIA/benchmarks) * [MLPerf Inference Benchmarks](https://github.com/mlcommons/inference_results_v2.0/tree/master/closed/NVIDIA/code) -### System Metrics -* [Performance Counters](./PerformanceCounterMetrics.md) -* [Power/Temperature Measurements](./PowerMetrics.md) + ### Workload-Specific Metrics The following metrics are captured during the operations of the MLPerf workload. diff --git a/website/docs/workloads/mlperf/MLPerfProfiles.md b/website/docs/workloads/mlperf/MLPerfProfiles.md index 83e3ad5f9..df2b6def3 100644 --- a/website/docs/workloads/mlperf/MLPerfProfiles.md +++ b/website/docs/workloads/mlperf/MLPerfProfiles.md @@ -3,8 +3,7 @@ The following profiles run customer-representative or benchmarking scenarios usi * [Workload Details](./MLPerf.md) * [Workload Profile Metrics](./MLPerfMetrics.md) -* [Workload Packages](./DependencyPackages.md) -* [Usage Scenarios/Examples](./UsageScenarios.md) + ----------------------------------------------------------------------- diff --git a/website/docs/workloads/nasparallel/NASParallelBenchMetrics.md b/website/docs/workloads/nasparallel/NASParallelBenchMetrics.md index bae192484..0651f6e7c 100644 --- a/website/docs/workloads/nasparallel/NASParallelBenchMetrics.md +++ b/website/docs/workloads/nasparallel/NASParallelBenchMetrics.md @@ -2,9 +2,7 @@ The following document illustrates the type of results that are emitted by the NAS Parallel workload and captured by the Virtual Client for net impact analysis. -### System Metrics -* [Performance Counters](./PerformanceCounterMetrics.md) -* [Power/Temperature Measurements](./PowerMetrics.md) + ### Workload-Specific Metrics diff --git a/website/docs/workloads/nasparallel/NASParallelBenchProfiles.md b/website/docs/workloads/nasparallel/NASParallelBenchProfiles.md index 0885c8644..2f3bea344 100644 --- a/website/docs/workloads/nasparallel/NASParallelBenchProfiles.md +++ b/website/docs/workloads/nasparallel/NASParallelBenchProfiles.md @@ -3,8 +3,7 @@ The following profiles run customer-representative or benchmarking scenarios usi * [Workload Details](./NASParallelBench.md) * [Workload Metrics](./NASParallelBenchs.md) -* [Workload Packages](./DependencyPackages.md) -* [Usage Scenarios/Examples](./UsageScenarios.md) + ----------------------------------------------------------------------- diff --git a/website/docs/workloads/network-ping/NetworkPingMetrics.md b/website/docs/workloads/network-ping/NetworkPingMetrics.md index 492b59d49..1df36faae 100644 --- a/website/docs/workloads/network-ping/NetworkPingMetrics.md +++ b/website/docs/workloads/network-ping/NetworkPingMetrics.md @@ -2,9 +2,7 @@ The following document illustrates the type of results that are emitted by the Network Ping workload and captured by the Virtual Client for net impact analysis. -### System Metrics -* [Performance Counters](./PerformanceCounterMetrics.md) -* [Power/Temperature Measurements](./PowerMetrics.md) + ### Workload-Specific Metrics The following metrics are emitted by the Network Ping workload itself. diff --git a/website/docs/workloads/network/NetworkSuiteMetrics.md b/website/docs/workloads/network/NetworkSuiteMetrics.md index 425a40551..e34beff79 100644 --- a/website/docs/workloads/network/NetworkSuiteMetrics.md +++ b/website/docs/workloads/network/NetworkSuiteMetrics.md @@ -2,9 +2,7 @@ The following document illustrates the type of results that are emitted by the Azure Networking benchmark workload suite and captured by the Virtual Client for net impact analysis. -### System Metrics -* [Performance Counters](./PerformanceCounterMetrics.md) -* [Power/Temperature Measurements](./PowerMetrics.md) + ### Workload-Specific Metrics The following metrics are emitted by the suite of Networking workloads. diff --git a/website/docs/workloads/network/NetworkSuiteProfiles.md b/website/docs/workloads/network/NetworkSuiteProfiles.md index 72200585a..9c3528d96 100644 --- a/website/docs/workloads/network/NetworkSuiteProfiles.md +++ b/website/docs/workloads/network/NetworkSuiteProfiles.md @@ -4,8 +4,7 @@ workload suite. * [Workload Details](./NetworkSuite.md) * [Workload Profile Metrics](./NetworkSuiteMetrics.md) -* [Workload Packages](./DependencyPackages.md) -* [Usage Scenarios/Examples](./UsageScenarios.md) + ----------------------------------------------------------------------- diff --git a/website/docs/workloads/openfoam/OpenFOAMMetrics.md b/website/docs/workloads/openfoam/OpenFOAMMetrics.md index 518df54fa..e32911a67 100644 --- a/website/docs/workloads/openfoam/OpenFOAMMetrics.md +++ b/website/docs/workloads/openfoam/OpenFOAMMetrics.md @@ -2,9 +2,7 @@ The following document illustrates the type of results that are emitted by the OpenFOAM workload and captured by the Virtual Client for net impact analysis. -### System Metrics -* [Performance Counters](./PerformanceCounterMetrics.md) -* [Power/Temperature Measurements](./PowerMetrics.md) + ### Workload-Specific Metrics The following metrics are emitted by the OpenFOAM workload itself. diff --git a/website/docs/workloads/openfoam/OpenFOAMProfiles.md b/website/docs/workloads/openfoam/OpenFOAMProfiles.md index d9fd1247b..4aafa5836 100644 --- a/website/docs/workloads/openfoam/OpenFOAMProfiles.md +++ b/website/docs/workloads/openfoam/OpenFOAMProfiles.md @@ -3,8 +3,7 @@ The following profiles run customer-representative or benchmarking scenarios usi * [Workload Details](./OpenFOAM.md) * [Workload Profile Metrics](./OpenFOAMMetrics.md) -* [Workload Packages](./DependencyPackages.md) -* [Usage Scenarios/Examples](./UsageScenarios.md) + ----------------------------------------------------------------------- diff --git a/website/docs/workloads/openssl/OpenSSLMetrics.md b/website/docs/workloads/openssl/OpenSSLMetrics.md index b8aa84259..4c5ef1c28 100644 --- a/website/docs/workloads/openssl/OpenSSLMetrics.md +++ b/website/docs/workloads/openssl/OpenSSLMetrics.md @@ -2,9 +2,7 @@ The following document illustrates the type of results that are emitted by the OpenSSL speed workload and captured by the Virtual Client for net impact analysis. -### System Metrics -* [Performance Counters](./PerformanceCounterMetrics.md) -* [Power/Temperature Measurements](./PowerMetrics.md) + ### Workload-Specific Metrics The following metrics are emitted by the OpenSSL speed workload itself. diff --git a/website/docs/workloads/openssl/OpenSSLProfiles.md b/website/docs/workloads/openssl/OpenSSLProfiles.md index cfbb52b26..fb0bb6255 100644 --- a/website/docs/workloads/openssl/OpenSSLProfiles.md +++ b/website/docs/workloads/openssl/OpenSSLProfiles.md @@ -3,8 +3,7 @@ The following profiles run customer-representative or benchmarking scenarios usi * [Workload Details](./OpenSSL.md) * [Workload Profile Metrics](./OpenSSLMetrics.md) -* [Workload Packages](./DependencyPackages.md) -* [Usage Scenarios/Examples](./UsageScenarios.md) + ----------------------------------------------------------------------- diff --git a/website/docs/workloads/prime95/Prime95Metrics.md b/website/docs/workloads/prime95/Prime95Metrics.md index 280e66e81..d08f870ca 100644 --- a/website/docs/workloads/prime95/Prime95Metrics.md +++ b/website/docs/workloads/prime95/Prime95Metrics.md @@ -2,9 +2,7 @@ The following document illustrates the type of results that are emitted by the Prime95 workload and captured by the Virtual Client for net impact analysis. -### System Metrics -* [Performance Counters](./PerformanceCounterMetrics.md) -* [Power/Temperature Measurements](./PowerMetrics.md) + ### Workload-Specific Metrics The following metrics are captured during the operations of the Prime95 workload. diff --git a/website/docs/workloads/prime95/Prime95Profiles.md b/website/docs/workloads/prime95/Prime95Profiles.md index 12cd9dc0a..426ac8441 100644 --- a/website/docs/workloads/prime95/Prime95Profiles.md +++ b/website/docs/workloads/prime95/Prime95Profiles.md @@ -4,8 +4,7 @@ The following profiles run customer-representative or benchmarking scenarios usi * [Workload Details](./Prime95.md) * [Workload Profile Metrics](./Prime95Metrics.md) -* [Workload Packages](./DependencyPackages.md) -* [Usage Scenarios/Examples](./UsageScenarios.md) + ----------------------------------------------------------------------- diff --git a/website/docs/workloads/redis/RedisMetrics.md b/website/docs/workloads/redis/RedisMetrics.md index e9c90ba04..e22950cbd 100644 --- a/website/docs/workloads/redis/RedisMetrics.md +++ b/website/docs/workloads/redis/RedisMetrics.md @@ -2,9 +2,7 @@ The following document illustrates the type of results that are emitted by the Redis workload and captured by the Virtual Client for net impact analysis. -### System Metrics -* [Performance Counters](./PerformanceCounterMetrics.md) -* [Power/Temperature Measurements](./PowerMetrics.md) + ### Workload-Specific Metrics diff --git a/website/docs/workloads/redis/RedisProfiles.md b/website/docs/workloads/redis/RedisProfiles.md index 86cd2d72e..e33662cbd 100644 --- a/website/docs/workloads/redis/RedisProfiles.md +++ b/website/docs/workloads/redis/RedisProfiles.md @@ -3,8 +3,7 @@ The following profiles run customer-representative or benchmarking scenarios usi * [Workload Details](./Redis.md) * [Workload Profile Metrics](./RedisMetrics.md) -* [Workload Packages](./DependencyPackages.md) -* [Usage Scenarios/Examples](./UsageScenarios.md) + ----------------------------------------------------------------------- diff --git a/website/docs/workloads/specjvm/SPECjvmMetrics.md b/website/docs/workloads/specjvm/SPECjvmMetrics.md index fb5aee723..8b414cc79 100644 --- a/website/docs/workloads/specjvm/SPECjvmMetrics.md +++ b/website/docs/workloads/specjvm/SPECjvmMetrics.md @@ -4,9 +4,7 @@ Virtual Client for net impact analysis. * [SPECjvm Benchmarks](https://www.spec.org/jvm2008/docs/benchmarks/index.html) -### System Metrics -* [Performance Counters](./PerformanceCounterMetrics.md) -* [Power/Temperature Measurements](./PowerMetrics.md) + ### Workload-Specific Metrics The following metrics are captured during the operations of the SuperBenchmark workload. diff --git a/website/docs/workloads/specjvm/SPECjvmProfiles.md b/website/docs/workloads/specjvm/SPECjvmProfiles.md index c49d73cb8..963bef216 100644 --- a/website/docs/workloads/specjvm/SPECjvmProfiles.md +++ b/website/docs/workloads/specjvm/SPECjvmProfiles.md @@ -3,8 +3,7 @@ The following profiles run customer-representative or benchmarking scenarios usi * [Workload Details](./SPECjvm.md) * [Workload Profile Metrics](./SPECjvmMetrics.md) -* [Workload Packages](./DependencyPackages.md) -* [Usage Scenarios/Examples](./UsageScenarios.md) + ----------------------------------------------------------------------- diff --git a/website/docs/workloads/stress-ng/StressNgMetrics.md b/website/docs/workloads/stress-ng/StressNgMetrics.md index 81daeb478..2b9f2c345 100644 --- a/website/docs/workloads/stress-ng/StressNgMetrics.md +++ b/website/docs/workloads/stress-ng/StressNgMetrics.md @@ -2,9 +2,7 @@ The following document illustrates the type of results that are emitted by the StressNg workload and captured by the Virtual Client for net impact analysis. -### System Metrics -* [Performance Counters](./PerformanceCounterMetrics.md) -* [Power/Temperature Measurements](./PowerMetrics.md) + ### Workload-Specific Metrics The following metrics are captured during the operations of the StressNg workload. diff --git a/website/docs/workloads/superbenchmark/SuperBenchmark.md b/website/docs/workloads/superbenchmark/SuperBenchmark.md index f389344fc..335ef98ad 100644 --- a/website/docs/workloads/superbenchmark/SuperBenchmark.md +++ b/website/docs/workloads/superbenchmark/SuperBenchmark.md @@ -1,6 +1,5 @@ --- id: superbenchmark -sidebar_position: 1 --- # SuperBenchmark Workload Suite diff --git a/website/docs/workloads/superbenchmark/SuperBenchmarkMetrics.md b/website/docs/workloads/superbenchmark/SuperBenchmarkMetrics.md index 53b2e4415..21db70d7a 100644 --- a/website/docs/workloads/superbenchmark/SuperBenchmarkMetrics.md +++ b/website/docs/workloads/superbenchmark/SuperBenchmarkMetrics.md @@ -6,9 +6,7 @@ Virtual Client for net impact analysis. * [SuperBenchmark ModelBenchmarks](https://microsoft.github.io/superbenchmark/docs/user-tutorial/benchmarks/model-benchmarks) * [SuperBenchmark DockerBenchmarks](https://microsoft.github.io/superbenchmark/docs/user-tutorial/benchmarks/docker-benchmarks) -### System Metrics -* [Performance Counters](./PerformanceCounterMetrics.md) -* [Power/Temperature Measurements](./PowerMetrics.md) + ### Workload-Specific Metrics The following metrics are captured during the operations of the SuperBenchmark workload. diff --git a/website/docs/workloads/superbenchmark/SuperBenchmarkProfiles.md b/website/docs/workloads/superbenchmark/SuperBenchmarkProfiles.md index cc0c093ce..3a2485cda 100644 --- a/website/docs/workloads/superbenchmark/SuperBenchmarkProfiles.md +++ b/website/docs/workloads/superbenchmark/SuperBenchmarkProfiles.md @@ -3,8 +3,7 @@ The following profiles run customer-representative or benchmarking scenarios usi * [Workload Details](./SuperBenchmark.md) * [Workload Profile Metrics](./SuperBenchmarkMetrics.md) -* [Workload Packages](./DependencyPackages.md) -* [Usage Scenarios/Examples](./UsageScenarios.md) + ----------------------------------------------------------------------- diff --git a/website/docusaurus.config.js b/website/docusaurus.config.js index 747b254f3..b176cf0f8 100644 --- a/website/docusaurus.config.js +++ b/website/docusaurus.config.js @@ -36,14 +36,14 @@ const config = { // Please change this to your repo. // Remove this to remove the "edit this page" links. editUrl: - 'https://github.com/microsoft/VirtualClient/edit/main', + 'https://github.com/microsoft/VirtualClient/edit/main/website', }, blog: { showReadingTime: true, // Please change this to your repo. // Remove this to remove the "edit this page" links. editUrl: - 'https://github.com/microsoft/VirtualClient/edit/main', + 'https://github.com/microsoft/VirtualClient/edit/main/website', }, theme: { customCss: require.resolve('./src/css/custom.css'),