📄️ Getting Started
The sections below will help the user install the Virtual Client
📄️ Getting Started (Client/Server)
The sections below provide an example for how to run a client/server workload. For this example, the Memtier + Redis workload will be used. It supports 2 roles (Client and Server),
📄️ Getting Started (Docker)
In this document, we are going to run OpenSSL workload in a Docker Container.
📄️ Command Line Options
The following sections describe the command line options available on the Virtual Client application.
📄️ Profiles
The Virtual Client defines the work/operations that will happen on a system in structured JSON documents called "profiles". Profiles can be thought
📄️ Client/Server Support
The Virtual Client supports workloads that run across more than 1 systems. These are often called "client/server" workloads. For example the networking
📄️ Run Commercial Workloads: Bring Your Own Package
Virtual Client supports running commercial workloads. However, we can not distribute the binary and licenses for the commercial workloads. In those cases, users need to "bring their own binary and license".
📄️ Data/Telemetry Support
The Virtual Client emits a range of different types of data/telemetry as part of the execution of workload and monitoring
📄️ Usage: Command Line Examples
The following documentation covers a range of usage scenarios that apply to the Virtual Client. The sections that follow are meant
📄️ Usage: Testing Disks
VC automates disk formating and run storage workloads on the target systems. We documented the rules and the mechanism we used to identify disks to run workloads on.
📄️ Disconnected Scenarios Support
Comming Soon
📄️ Azure Storage Account Integration
Virtual Client supports a few different types of Azure Blob stores that can be used as part of a workload profile execution. This documentation
📄️ Azure Event Hub Integration
Azure Event Hubs is a highly scalable Azure cloud messaging hub/proxy that has out-of-the-box integration with a number of other Azure data/data