Skip to content

Latest commit

 

History

History
100 lines (85 loc) · 5.03 KB

README.md

File metadata and controls

100 lines (85 loc) · 5.03 KB
Raw

DistIR

An IR to represent distributed computations. Our main goal is an IR capable of representing the complex distributed strategies used in large-scale distributed training, while at the same time enabling fast cost models/simulations.

Distributed strategies we want to support:

  • Data parallelism
  • Horizontal parallelism
  • Pipeline parallelism
  • Megatron
  • ZeRO partitioning
  • PyTorch lightning's Zero
  • Stashing & recomputation
  • Overlapping computation and communication
  • Local layer parallelism

Requirements/Installation

See the build file and PIP packages list.

Directory structure

  • dist_ir: Python source for DistIR
    • ir: IR definitions
    • importer: create DistIR from ONNX/MLIR
    • executor: ways to "execute" or simulate DistIR
  • docs: documentation and notes
  • notebooks: small experiments and worked examples
  • test: unit tests, small/toy example models

Running tests

Run the following from the root of this repository:

python -m pytest

Components

  • Executors:
    • SequentialExecutor: a reference implementation that runs a DistIR function on a single device. Can be used to check correctness of transforms.
    • DistributedSimulator: an executor that uses profile data or flop counts to simulate the execution of a given DistIR function on a given hardware configuration (including communication bandwidths and processor speed). Returns estimated execution time and live memory profile. This can be split into three subcomponents:
      • Shape Inference: a pass that uses the shapes of inputs to calculate the shapes of all intermediate values.
      • Cost Inference: a pass that uses either shape information to compute (or profiles the function and measures) the runtime and temporary memory requirement of each op in the function. This output can be cached.
      • Simulator: takes a function and a mapping from op to time/memory consumption and does a simulation to obtain a concurrent trace (from which total runtime and memory usage plots can be derived).
  • Importers:
    • ONNX Importer: convert a .onnx file to a DistIR function. Can be given an intermediate graph from ORT (for example, after AD).
    • MLIR Importer: import a DistIR function written in MLIR text format to an in-memory DistIR function object. TODO
  • Exporter/Prettyprinter: converts a DistIR function to an MLIR text format string.
  • Transforms: a module containing DistIR->DistIR transforms. Ideally, these transforms should be composable and should run on subfunctions so that we can have nested parallelism (data parallel where a subset of the layers are horizontal parallel, or pipeline parallel where each stage is data parallel with a different degree).
    • DataParallelTransform: converts a given DistIR function to a data-parallel version that runs on a given number of devices.
    • HorizontalParallelTransform: converts a given DistIR function to a horizontal-parallel version (if possible) that runs on a given number of devices.
    • PipelineParallelTransform: converts a given DistIR function to a pipeline-parallel version that runs on a given number of devices.
  • Search: an algorithm to find the best distributed version of a given sequential DistIR function. Initially, this can be something that searches the DHP space (i.e. find the optimal parameters to give the D/H/P transforms).

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repositories using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Trademarks: This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.