Developer Guide

  • 2021.1
  • 11/03/2021
  • Public

Tuning Configuration File

The preproduction tool generates a tuning configuration file after finding a tuning configuration that meets requirements. You can use the file to apply the configuration to the production environment via the production tool. The format of the file is JSON.
Do not edit the contents of the file. Editing the file may lead to unexpected results.

JSON Description

Example tuning configuration file:
{ "specification": { "workload": { "command": "python3 /usr/share/tcc_tools/tools/demo/workloads/bin/", "arguments": [ "--latency_us 100 ", "--ssh root@", "--pci_rtcp 0000:01:00.0", "--pci_pglm 0000:01:00.0", "--no-compute", "--cpuid 3" ] }, "requirements": [ { "producer": "Memory", "consumer": "01:00.0", "traffic_class": 0, "latency_us": 4, "bytes_per_transfer": 64, "relative_priority": 0 } ] }, "capsule_apply_command": "fwupdate --apply bf2ae378-01e0-4605-9e3b-2ee2fc7339de /home/root/streams_capsule.out.bin", "reboot_command": "reboot", "capsule": "<binary>" }
The file contains the following information:
  • "specification"
    : Contains a copy of the requirements file that was input in the preproduction tool.
  • "capsule_apply_command"
    : Contains the value from the environment file.
  • "reboot_command"
    : Contains the value from the environment file
  • "capsule"
    : The Capsule. The image contains machine-readable data according to the specification of data communication between the data streams optimizer and BIOS. In addition, the capsule field is converted to text encoding from binary because JSON format expects text data only.

Product and Performance Information


Performance varies by use, configuration and other factors. Learn more at