Skip to main content

LMbench Workload Profiles

The following profiles run customer-representative or benchmarking scenarios using the LMbench workload.

PERF-MEM-LMBENCH.json​

Runs a memory-intensive workload using the LMbench toolset to test the performance of the system RAM/memory. This profile is designed to identify general/broad regressions when compared against a baseline.

  • Workload Profile

  • Supported Platform/Architectures

    • linux-x64
    • linux-arm64

  • Supports Disconnected Scenarios

    • No. Internet connection required.

  • Dependencies
    The dependencies defined in the 'Dependencies' section of the profile itself are required in order to run the workload operations effectively.

    • Internet connection.

    Additional information on components that exist within the 'Dependencies' section of the profile can be found in the following locations:

  • Profile Parameters
    The following parameters can be optionally supplied on the command line to modify the behaviors of the workload.

    ParameterPurposeDefault value
    CompilerNameOptional. The name of the compiler to use for compiling CoreMark on the system.gcc
    CompilerVersionOptional. The version of the compiler to use.10
    CompilerParametersOptional. The parameters that will be passed to the compiler.-O3 $ARRAY_FLAG -fopenmp -march=native -DNTIMES=5000

  • Profile Runtimes
    See the 'Metadata' section of the profile for estimated runtimes. These timings represent the length of time required to run a single round of profile actions. These timings can be used to determine minimum required runtimes for the Virtual Client in order to get results. These are often estimates based on the number of system cores.

  • Usage Examples
    The following section provides a few basic examples of how to use the workload profile. Additional usage examples can be found in the 'Usage Scenarios/Examples' link at the top.

    # Execute the workload profile
    VirtualClient.exe --profile=PERF-MEM-LMBENCH.json --system=Demo --timeout=1440 --packageStore="{BlobConnectionString|SAS Uri}"