DALI Release 1.10.0

Using DALI 1.10.0

To upgrade to DALI 1.10.0 from an older version of DALI, follow the installation and usage information in the DALI User Guide.

Note: The internal DALI C++ API used for operator’s implementation, and the C++ API that enables using DALI as a library from native code, is not yet officially supported. Hence these APIs may change in the next release without advance notice.

Key Features and Enhancements

This DALI release includes the following key features and enhancements:

  • New operators:
    • The get_property operator (CPU and GPU), which is used to fetch tensor metadata, such as the source file name (#3572).
    • The laplacian operator (CPU) (#3563).
  • Color-based augmentations were extended to support video data (#3580).
  • Improved performance of the slice operator (#3584, #3573, and #3568).
  • Added an experimental debug (immediate execution) mode (#3586 and #3531).

Fixed Issues

No major issues were fixed in this release.

Breaking Changes

There are no breaking changes in this DALI release.

Deprecated Features

There are no deprecated features in this DALI release.

Known Issues

This DALI release includes the following known issues:

  • The video loader operator requires that the key frames occur, at a minimum, every 10 to 15 frames of the video stream.

    If the key frames occur at a frequency that is less than 10-15 frames, the returned frames might be out of sync.

  • The DALI TensorFlow plug-in might not be compatible with TensorFlow versions 1.15.0 and later.

    To use DALI with the TensorFlow version that does not have the prebuilt plug-in binary that is shipped with DALI, ensure that the compiler that is used to build TensorFlow exists on the system during the plug-in installation. (Depending on the particular version, you can use GCC 4.8.4, GCC 4.8.5, or GCC 5.4.)

  • Due to some known issues with meltdown/spectra mitigations and DALI, DALI shows the best performance when running in Docker with escalated privileges, for example:
    • privileged=yes in Extra Settings for AWS data points
    • --privileged or --security-opt seccomp=unconfined for bare Docker