Runtime Environment Variables

The following table describes runtime environment variables that are set to change the behavior as well as enable or disable some features. Among the below flags, TF_NUM_INTEROP_THREADS, TF_CPP_MIN_LOG_LEVEL, and TF_CPP_MIN_VLOG_LEVEL are native TensorFlow flags. All other flags are SynapseAI specific.

Flag

Default

Description

TF_PLACE_ON_CPU

Unset

Accepts a comma-separated list of op types to be placed on the CPU by PlaceUnsupportedOpsOnCpu pass. If set to “all_nodes”, all nodes in the graph are placed on the CPU.

HBN_TF_GRAPH_DUMP

1

Controls dumping of TensorFlow graphs after different graph transformation phases.

  • 1 (default) - dumps only from POST_REWRITE_FOR_EXEC

  • 0 - disable dumping

  • Value above 1 - enables dumping from all phases

TF_DUMP_GRAPH_PREFIX

Unset

Sets the path that TensorFlow dumps are saved to.

If unset, graphs will not be dumped. A warning message is shown for built-in TF graph dumping.

ENABLE_CONSOLE

false

If set to ‘true’, enables printing Synapse_AI logs console.

LOG_LEVEL_ALL

5

Logging level from SynapseAI and perf_lib.

  • 6 is no logs

  • 0 is verbose

By default, logs are placed either in the console (if ENABLE_CONSOLE=true) or under ~/.habana_logs/.

TF_BF16_CONVERSION

Unset

Enables FP32 to BF16 conversion pass for mixed precision training. Currently supported settings:

  • ‘0’, ‘false’ or unset - conversion is disabled

  • ‘1’, ‘true’, ‘full’ - contains all convertible ops

  • ‘basic’ - only general matrix multiplications and convolutions are allowed

  • /path/to/model/mixed_precision_config.json

TF_BF16_DUMP_PATH

Unset

Allows dumping current BF16 config to JSON file. If set to an absolute path output file, data is dumped.

TF_ENABLE_DYNAMIC_SHAPES

True

If set to ‘false’ or ‘0’ support for compiling clusters with dynamic shape inputs is disabled.

Dynamic shapes are understood as inputs to the clusters, that are changing between iterations, forcing recompilations of graph recipes. Support of dynamic shapes reduces required number of recompilations by introducing graph recipes with input shape ranges (min,max) based on patterns of input shapes to a given cluster.

Disabling dynamic shapes support forces all clusters to be compiled statically, which can increase overall number of compilations.

TF_ENABLE_PATTERN_MATCHER

Unset

If set to ‘0’, Pattern Matcher optimization pass is disabled.

HABANA_INITIAL_WORKSPACE_SIZE_MB

Unset

Allows setting initial allocated memory size for workspace buffer in MB. That option is mainly for cases in which dynamic workspace allocation does not work properly.

TF_CPU_ALLOCATOR_SIZE_G

Unset

Default allocation strategy which allocates host memory with the below minimum values:

  • 64G (for machines with more than that)

  • 80% of available memory size

  • Available memory size - 16G

If this flag is set to any value, it instructs Habana CPU allocator to override the default configuration of the CPU memory pool size with the given size in Gigabytes.

TF_NUM_INTEROP_THREADS

Unset

If set to a non-zero value, this flag enforces the thread count for TensorFlow op execution. Otherwise, TensorFlow selects the count based on the available cores and MKL/OpenMP configurations.

TF_CPP_MIN_LOG_LEVEL

0

Logging level from native TensorFlow. Lower value means more logs. Valid values range is [0-4].

TF_CPP_MIN_VLOG_LEVEL

0

Another logging level from native TensorFlow. Higher value means more logs. Valid value range is [0-10].

TF_HABANA_ALLOW_LEGACY_VARIABLES_ON_CPU

False

If set to ‘True’, disables legacy Variables registration on HPU and allows them to be executed on CPU. Otherwise, legacy variables registration on HPU will prevent them from being executed at all.

TF_RECIPE_CACHE_PATH

Unset

Path (directory), where compiled graph recipes are stored between different runs of the same model (accelerates time of first iteration).

If unset, compiled graph recipes are not stored on disk (recipe disk caching disabled).

In a scale up scenario, different processes on one platform may share the same directory for recipe cache. Only one process compiles the recipe, and other processes read it from disk.

Note: Recipe cache dir is not cleared automatically and can increase in size over time.

Note: If a recipe cache is shared among a few processes (scale up), it must be stored on a local physical disk. Avoid using remote drives (such as NFS) where file locks are not supported, as it it may lead to instability and unpredictable behavior.