Unlock Efficient Business Operations with Accelerate 1.0.0: Streamline Processes and Amplify Productivity

Introduction

Accelerate, a simple framework designed to make training on multi-GPU and TPU systems easier, has evolved significantly over the past three and a half years. From its humble beginnings as a low-level abstraction simplifying a raw PyTorch training loop, Accelerate has expanded into a multi-faceted library tackling common problems with large-scale training and large models.

Accelerate’s Evolution

3.5 years ago, Accelerate was a simple framework aimed at making training on multi-GPU and TPU systems easier by having a low-level abstraction that simplified a raw PyTorch training loop:

Since then, Accelerate has expanded into a multi-faceted library aimed at tackling many common problems with large-scale training and large models in an age where 405 billion parameters (Llama) are the new language model size. This involves:

• A flexible low-level training API, allowing for training on six different hardware accelerators (CPU, GPU, TPU, XPU, NPU, MLU) while maintaining 99% of your original training loop
• An easy-to-use command-line interface aimed at configuring and running scripts across different hardware configurations
• The birthplace of Big Model Inference or device_map="auto", allowing users to not only perform inference on LLMs with multi-devices but now also aiding in training LLMs on small compute through techniques like parameter-efficient fine-tuning (PEFT)

These three facets have allowed Accelerate to become the foundation of nearly every package at Hugging Face, including transformers, diffusers, peft, trl, and more!

As the package has been stable for nearly a year, we’re excited to announce that, as of today, we’ve published the first release candidates for Accelerate 1.0.0!

Why 1.0?

The plans to release 1.0.0 have been in the works for over a year. The API has been roughly at a point where we wanted, centering on the Accelerator side, simplifying much of the configuration and making it more extensible. However, we knew there were a few missing pieces before we could call the “base” of Accelerate “feature complete”:

With the changes made for 1.0, accelerate is prepared to tackle new tech integrations while keeping the user-facing API stable.

The Future of Accelerate

Now that 1.0 is almost done, we can focus on new techniques coming out throughout the community and find integration paths into Accelerate, as we foresee some radical changes in the PyTorch ecosystem very soon:

• As part of the multiple-model DeepSpeed support, we found that while generally how DeepSpeed is currently could work, some heavy changes to the overall API may eventually be needed as we work to support simple wrappings to prepare models for any multiple-model training scenario.
• With torchao and torchtitan picking up steam, they hint at the future of PyTorch as a whole. Aiming at more native support for FP8 training, a new distributed sharding API, and support for a new version of FSDP, FSDPv2, we predict that much of the internals and general usage API of Accelerate will need to change (hopefully not too drastic) to meet these needs as the frameworks slowly become more stable.
• Riding on torchao/FP8, many new frameworks are bringing in different ideas and implementations on how to make FP8 training work and be stable (transformer_engine, torchao, MS-AMP, nanotron, to name a few). Our aim with Accelerate is to house each of these implementations in one place with easy configurations to let users explore and test out each one as they please, intending to find the ones that wind up being the most stable and flexible. It’s a rapidly accelerating (no pun intended) field of research, especially with NVIDIA’s FP4 training support on the way, and we want to make sure that not only can we support each of these methods but aim to provide solid benchmarks for each to show their tendencies out-of-the-box (with minimal tweaking) compared to native BF16 training

We’re incredibly excited about the future of distributed training in the PyTorch ecosystem, and we want to make sure that Accelerate is there every step of the way, providing a lower barrier to entry for these new techniques. By doing so, we hope the community will continue experimenting and learning together as we find the best methods for training and scaling larger models on more complex computing systems.

How to Try It Out

To try the first release candidate for Accelerate today, please use one of the following methods:

pip install --pre accelerate

docker pull huggingface/accelerate:gpu-release-1.0.0rc1

Valid release tags are:

• gpu-release-1.0.0rc1
• cpu-release-1.0.0rc1
• gpu-fp8-transformerengine-release-1.0.0rc1
• gpu-deepspeed-release-1.0.0rc1

Migration Assistance

Below are the full details for all deprecations that are being enacted as part of this release:

• Passing in dispatch_batches, split_batches, even_batches, and use_seedable_sampler to the Accelerator() should now be handled by creating an accelerate.utils.DataLoaderConfiguration() and passing this to the Accelerator() instead (Accelerator(dataloader_config=DataLoaderConfiguration(...)))
• Accelerator().use_fp16 and AcceleratorState().use_fp16 have been removed; this should be replaced by checking accelerator.mixed_precision == "fp16"
• Accelerator().autocast() no longer accepts a cache_enabled argument. Instead, an AutocastKwargs() instance should be used which handles this flag (among others) passing it to the Accelerator (Accelerator(kwargs_handlers=[AutocastKwargs(cache_enabled=True)]))
• accelerate.utils.is_tpu_available should be replaced with accelerate.utils.is_torch_xla_available
• accelerate.utils.modeling.shard_checkpoint should be replaced with split_torch_state_dict_into_shards from the huggingface_hub library
• accelerate.tqdm.tqdm() no longer accepts True/False as the first argument, and instead, main_process_only should be passed in as a named argument
• ACCELERATE_DISABLE_RICH is no longer a valid environmental variable, and instead, one should manually enable rich traceback by setting ACCELERATE_ENABLE_RICH=1
• The FSDP setting fsdp_backward_prefetch_policy has been replaced with fsdp_backward_prefetch

Closing Thoughts

Thank you so much for using Accelerate; it’s been amazing watching a small idea turn into over 100 million downloads and nearly 300,000 daily downloads over the last few years.

With this release candidate, we hope to give the community an opportunity to try it out and migrate to 1.0 before the official release.

Please stay tuned for more information by keeping an eye on the github and on socials!

Frequently Asked Questions

Question 1: What is Accelerate?

Accelerate is a simple framework designed to make training on multi-GPU and TPU systems easier by having a low-level abstraction that simplifies a raw PyTorch training loop.

Question 2: What are the key features of Accelerate?

Accelerate’s key features include a flexible low-level training API, an easy-to-use command-line interface, and the birthplace of Big Model Inference or device_map="auto".

Question 3: What is the future of Accelerate?

The future of Accelerate is to house each of the new implementations in one place with easy configurations to let users explore and test out each one as they please, intending to find the ones that wind up being the most stable and flexible.

Question 4: How do I try out the first release candidate for Accelerate?

To try the first release candidate for Accelerate, please use one of the following methods: pip install --pre accelerate or docker pull huggingface/accelerate:gpu-release-1.0.0rc1.

Question 5: What are the deprecations in this release?

The deprecations in this release include passing in dispatch_batches, split_batches, even_batches, and use_seedable_sampler to the Accelerator(), Accelerator().use_fp16 and AcceleratorState().use_fp16, and more.

Conclusion

Accelerate has come a long way since its humble beginnings as a simple framework designed to make training on multi-GPU and TPU systems easier. With its first release candidate for 1.0.0, we’re excited to give the community an opportunity to try it out and migrate to 1.0 before the official release. Stay tuned for more information by keeping an eye on the github and on socials!