Skip to content

Releases: huggingface/accelerate

v0.6.0: Checkpointing and bfloat16 support

18 Mar 13:47
Compare
Choose a tag to compare

This release adds support for bloat16 mixed precision training (requires PyTorch >= 1.10) and a brand-new checkpoint utility to help with resuming interrupted trainings. We also get a completely revamped documentation frontend.

Checkpoints

Save the current state of all your objects (models, optimizers, RNG states) with accelerator.save_state(path_to_checkpoint) and reload everything by calling accelerator.load_state(path_to_checkpoint)

BFloat16 support

Accelerate now supports bfloat16 mixed precision training. As a result the old --fp16 argument has been deprecated to be replaced by the more generic --mixed-precision.

New env subcommand

You can now type accelerate env to have a copy-pastable summary of your environment and default configuration. Very convenient when opening a new issue!

New doc frontend

The documentation has been switched to the new Hugging Face frontend, like Transformers and Datasets.

  • Convert documentation to the new front by @sgugger in #271

What's Changed

New Contributors

Full Changelog: v0.5.1...v0.6.0

v0.5.1: Patch release

27 Sep 15:05
Compare
Choose a tag to compare

v0.5.1: Patch release

Fix the two following bugs:

  • convert_to_fp32 returned booleans instead of tensors #173
  • wrong dataloader lenght when dispatch_batches=True #175

v0.5.0 Dispatch batches from main DataLoader

23 Sep 14:38
Compare
Choose a tag to compare

v0.5.0 Dispatch batches from main DataLoader

This release introduces support for iterating through a DataLoader only on the main process, that then dispatches the batches to all processes.

Dispatch batches from main DataLoader

The motivation behind this come from dataset streaming which introduces two difficulties:

  • there might be some timeouts for some elements of the dataset, which might then be different in each process launched, thus it's impossible to make sure the data is iterated though the same way on each process
  • when using IterableDataset, each process goes through the dataset, thus applies the preprocessing on all elements. This can yield to the training being slowed down by this preprocessing.

This new feature is activated by default for all IterableDataset.

Various fixes

v0.4.0 Experimental DeepSpeed and multi-node CPU support

10 Aug 09:46
Compare
Choose a tag to compare

v0.4.0 Experimental DeepSpeed support

This release adds support for DeepSpeed. While the basics are there to support ZeRO-2, ZeRo-3, as well a CPU and NVME offload, the API might evolve a little bit as we polish it in the near future.

It also adds support for multi-node CPU. In both cases, just filling the questionnaire outputted by accelerate config and then launching your script with accelerate launch is enough, there are no changes in the main API.

DeepSpeed support

  • Add DeepSpeed support #82 (@vasudevgupta7)
  • DeepSpeed documentation #140 (@sgugger)

Multinode CPU support

  • Add distributed multi-node cpu only support (MULTI_CPU) #63 (@ddkalamk)

Various fixes

v0.3.0 Notebook launcher and multi-node training

29 Apr 15:45
Compare
Choose a tag to compare

v0.3.0 Notebook launcher and multi-node training

Notebook launcher

After doing all the data preprocessing in your notebook, you can launch your training loop using the new notebook_launcher functionality. This is especially useful for Colab or Kaggle with TPUs! Here is an example on Colab (don't forget to select a TPU runtime).

This launcher also works if you have multiple GPUs on your machine. You just have to pass along num_processes=your_number_of_gpus in the call to notebook_launcher.

Multi-node training

Our multi-node training test setup was flawed and the previous releases of 🤗 Accelerate were not working for multi-node distributed training. This is all fixed now and we have ensured to have more robust tests!

Various bug fixes

v0.2.1: Patch release

19 Apr 17:32
Compare
Choose a tag to compare

Fix a bug preventing the load of a config with accelerate launch

v0.2.0 SageMaker launcher

15 Apr 16:00
Compare
Choose a tag to compare

v0.2.0 SageMaker launcher

SageMaker launcher

It's now possible to launch your training script on AWS instances using SageMaker via accelerate launch.

Kwargs handlers

To customize how the different objects used for mixed precision or distributed training are instantiated, a new API called KwargsHandler is added. This allows the user to pass along the kwargs that will be passed to those objects if used (and it is ignored if those are not used in the current setup, so the script can still run on any kind of setup).

Pad across processes

Trying to gather tensors that are not of the same size across processes resulted in a process hang, a new method Accelerator.pad_across_processes has been added to help with that.

  • Add utility to pad tensor across processes to max length #19 (@sgugger )

Various bug fixes

v0.1.0 Initial release

05 Mar 21:59
Compare
Choose a tag to compare

Initial release of 🤗 Accelerate. Checkout the main README or the docs to learn more about it!