Run training on Amazon SageMaker¶
Hugging Face and Amazon are introducing new Hugging Face Deep Learning Containers (DLCs) to make it easier than ever to train Hugging Face Transformer models in Amazon SageMaker.
To learn how to access and use the new Hugging Face DLCs with the Amazon SageMaker Python SDK, check out the guides and resources below.
Deep Learning Container (DLC) overview¶
The Deep Learning Container are in every available where Amazon SageMaker is available. You can see the AWS region table for all AWS global infrastructure. To get an detailed overview of all included packages look here in the release notes.
🤗 Transformers version | 🤗 Datasets version | PyTorch/TensorFlow version | type | device | Python Version | Example image_uri |
---|---|---|---|---|---|---|
4.4.2 | 1.5.0 | PyTorch 1.6.0 | training | GPU | 3.6 | 763104351884.dkr.ecr.us-west-2.amazonaws.com/huggingface-pytorch-training:1.6.0-transformers4.4.2-gpu-py36-cu110-ubuntu18.04 |
4.4.2 | 1.5.0 | TensorFlow 2.4.1 | training | GPU | 3.7 | 763104351884.dkr.ecr.us-west-2.amazonaws.com/huggingface-tensorflow-training:2.4.1-transformers4.4.2-gpu-py37-cu110-ubuntu18.04 |
Getting Started: Train a 🤗 Transformers Model¶
To train a 🤗 Transformers model by using the HuggingFace
SageMaker Python SDK you need to:
Setup & Installation¶
Before you can train a transformers models with Amazon SageMaker you need to sign up for an AWS account. If you do not have an AWS account yet learn more here.
After you complete these tasks you can get started using either SageMaker Studio, SageMaker Notebook Instances, or a local environment. To start training locally you need configure the right IAM permission.
Upgrade to the latest sagemaker
version.
pip install sagemaker --upgrade
SageMaker environment
Note: The execution role is intended to be available only when running a notebook within SageMaker. If you run get_execution_role
in a notebook not on SageMaker, expect a “region” error.
import sagemaker
sess = sagemaker.Session()
role = sagemaker.get_execution_role()
Local environment
iam_client = boto3.client('iam')
role = iam_client.get_role(RoleName='role-name-of-your-iam-role-with-right-permissions')['Role']['Arn']
sess = sagemaker.Session()
Prepare a 🤗 Transformers fine-tuning script.¶
The training script is very similar to a training script you might run outside of SageMaker, but you can access useful properties about the training environment through various environment variables, including the following:
SM_MODEL_DIR
: A string that represents the path where the training job writes the model artifacts to. After training, artifacts in this directory are uploaded to S3 for model hosting.SM_MODEL_DIR
is always set to/opt/ml/model
.SM_NUM_GPUS
: An integer representing the number of GPUs available to the host.SM_CHANNEL_XXXX:
A string that represents the path to the directory that contains the input data for the specified channel. For example, if you specify two input channels in the HuggingFace estimator’s fit call, namedtrain
andtest
, the environment variablesSM_CHANNEL_TRAIN
andSM_CHANNEL_TEST
are set.
You can find a full list of the exposed environment variables here.
Later we define hyperparameters
in the HuggingFace Estimator, which are passed in as named arguments and and can be processed with the ArgumentParser()
.
import transformers
import datasets
import argparse
import os
if __name__ == "__main__":
parser = argparse.ArgumentParser()
# hyperparameters sent by the client are passed as command-line arguments to the script.
parser.add_argument("--epochs", type=int, default=3)
parser.add_argument("--per_device_train_batch_size", type=int, default=32)
parser.add_argument("--model_name_or_path", type=str)
# Data, model, and output directories
parser.add_argument("--model-dir", type=str, default=os.environ["SM_MODEL_DIR"])
parser.add_argument("--training_dir", type=str, default=os.environ["SM_CHANNEL_TRAIN"])
parser.add_argument("--test_dir", type=str, default=os.environ["SM_CHANNEL_TEST"])
Note that SageMaker doesn’t support argparse actions. For example, if you want to use a boolean hyperparameter, specify type
as bool
in your script and provide an explicit True
or False
value.
For a complete example of a 🤗 Transformers training script, see train.py
Create an HuggingFace Estimator¶
You run 🤗 Transformers training scripts on SageMaker by creating HuggingFace
Estimators. The Estimator handles end-to-end Amazon SageMaker training. The training of your script is invoked when you call fit
on a HuggingFace
Estimator. In the Estimator you define, which fine-tuning script should be used as entry_point
, which instance_type
should be used, which hyperparameters
are passed in, you can find all possible HuggingFace
Parameter here. and an example of a fine-tuning script here.
You can find all useable instance_types
here.
The following code sample shows how you train a custom HuggingFace
script train.py
, passing in three hyperparameters (epochs
, per_device_train_batch_size
, and model_name_or_path
).
from sagemaker.huggingface import HuggingFace
# hyperparameters, which are passed into the training job
hyperparameters={'epochs': 1,
'per_device_train_batch_size': 32,
'model_name_or_path': 'distilbert-base-uncased'
}
# create the Estimator
huggingface_estimator = HuggingFace(
entry_point='train.py',
source_dir='./scripts',
instance_type='ml.p3.2xlarge',
instance_count=1,
role=role,
transformers_version='4.4',
pytorch_version='1.6',
py_version='py36',
hyperparameters = hyperparameters
)
To run the TrainingJob
locally you can define instance_type='local'
or instance_type='local-gpu'
for gpu usage. Note: this does not working within SageMaker Studio
Execute Training¶
You start your TrainingJob
by calling fit
on a HuggingFace
Estimator. In the fit
method you specify your input training data, like a string S3 URI s3://my-bucket/my-training-data
or a FileSystemInput
for EFS or FSx Lustre, see here.
huggingface_estimator.fit(
{'train': 's3://sagemaker-us-east-1-558105141721/samples/datasets/imdb/train',
'test': 's3://sagemaker-us-east-1-558105141721/samples/datasets/imdb/test'}
)
SageMaker takes care of starting and managing all the required ec2 instances for ands starts the training job by running.
/opt/conda/bin/python train.py --epochs 1 --model_name_or_path distilbert-base-uncased --per_device_train_batch_size 32
Access trained model¶
After training is done you can access your model either through the AWS console or downloading it directly from S3.
from sagemaker.s3 import S3Downloader
S3Downloader.download(
s3_uri=huggingface_estimator.model_data, # s3 uri where the trained model is located
local_path='.', # local path where *.targ.gz is saved
sagemaker_session=sess # sagemaker session used for training the model
)
Sample Notebooks¶
You can find here a list of the official notebooks provided by Hugging Face.
Notebook | Description |
---|---|
Getting Started Pytorch | End-to-End binary Text-Classification example using Trainer and imdb dataset |
Getting Started Tensorflow | End-to-End binary Text-Classification example using Keras and imdb dataset |
Distributed Training Data Parallelism | End-to-End distributed Question-Answering example using Trainer and 🤗 Transformers example script for SQAuD |
Distributed Training Model Parallelism | End-to-End model parallelism example using SageMakerTrainer and run_glue.py script |
Spot Instances and continues training | End-to-End to Text-Classification example using spot instances with continued training. |
SageMaker Metrics | End-to-End to Text-Classification example using SageMaker Metrics to extract and log metrics during training |
Distributed Training Data Parallelism Tensorflow | End-to-End distributed binary Text-Classification example using Keras and TensorFlow |
Advanced Features¶
In addition to the Deep Learning Container and the SageMaker SDK, we have implemented other additional features.
Distributed Training: Data-Parallel¶
You can use SageMaker Data Parallelism Library out of the box for distributed training. We added the functionality of Data Parallelism directly into the Trainer. If your train.py uses the Trainer API you only need to define the distribution parameter in the HuggingFace Estimator.
# configuration for running training on smdistributed Data Parallel
distribution = {'smdistributed':{'dataparallel':{ 'enabled': True }}}
# create the Estimator
huggingface_estimator = HuggingFace(
entry_point='train.py',
source_dir='./scripts',
instance_type='ml.p3dn.24xlarge',
instance_count=2,
role=role,
transformers_version='4.4.2',
pytorch_version='1.6.0',
py_version='py36',
hyperparameters = hyperparameters
distribution = distribution
)
Distributed Training: Model-Parallel¶
You can use SageMaker Model Parallelism Library out of the box for distributed training. We extended the Trainer API to the SageMakerTrainer to use the model parallelism library. Therefore you only have to change the imports in your train.py
.
from transformers.sagemaker import SageMakerTrainingArguments as TrainingArguments
from transformers.sagemaker import SageMakerTrainer as Trainer
After the adjustments in the train.py you need to extend the distribution configuration in the HuggingFace Estimator. For detailed information about the adjustments take a look here.
# configuration for running training on smdistributed Model Parallel
mpi_options = {
"enabled" : True,
"processes_per_host" : 8
}
smp_options = {
"enabled":True,
"parameters": {
"microbatches": 4,
"placement_strategy": "spread",
"pipeline": "interleaved",
"optimize": "speed",
"partitions": 4,
"ddp": True,
}
}
distribution={
"smdistributed": {"modelparallel": smp_options},
"mpi": mpi_options
}
# create the Estimator
huggingface_estimator = HuggingFace(
entry_point='train.py',
source_dir='./scripts',
instance_type='ml.p3dn.24xlarge',
instance_count=2,
role=role,
transformers_version='4.4.2',
pytorch_version='1.6.0',
py_version='py36',
hyperparameters = hyperparameters
distribution = distribution
)
Spot Instances¶
With the creation of HuggingFace Framework extension for the SageMaker Python SDK we can also leverage the benefit of fully-managed EC2 spot instances and save up to 90% of our training cost.
Note: Unless your training job completes quickly, we recommend you use checkpointing with managed spot training, therefore you need to define the checkpoint_s3_uri
.
To use spot instances with the HuggingFace
Estimator we have to set the use_spot_instances
parameter to True
and define your max_wait
and max_run
time. You can read more about the managed spot training lifecycle here.
# hyperparameters, which are passed into the training job
hyperparameters={'epochs': 1,
'train_batch_size': 32,
'model_name':'distilbert-base-uncased',
'output_dir':'/opt/ml/checkpoints'
}
# create the Estimator
huggingface_estimator = HuggingFace(
entry_point='train.py',
source_dir='./scripts',
instance_type='ml.p3.2xlarge',
instance_count=1,
checkpoint_s3_uri=f's3://{sess.default_bucket()}/checkpoints'
use_spot_instances=True,
max_wait=3600, # This should be equal to or greater than max_run in seconds'
max_run=1000,
role=role,
transformers_version='4.4',
pytorch_version='1.6',
py_version='py36',
hyperparameters = hyperparameters
)
# Training seconds: 874
# Billable seconds: 262
# Managed Spot Training savings: 70.0%
Git Repository¶
When you create a HuggingFace
Estimator, you can specify a training script that is stored in a GitHub repository as the entry point for the estimator, so that you don’t have to download the scripts locally. If Git support is enabled, then entry_point
and source_dir
should be relative paths in the Git repo if provided.
As an example to use git_config
with an example script from the transformers repository.
Tip: define output_dir
as /opt/ml/model
in the hyperparameter for the script to save your model to S3 after training.
# configure git settings
git_config = {'repo': 'https://github.com/huggingface/transformers.git','branch': 'master'}
# create the Estimator
huggingface_estimator = HuggingFace(
entry_point='run_glue.py',
source_dir='./examples/text-classification',
git_config=git_config,
instance_type='ml.p3.2xlarge',
instance_count=1,
role=role,
transformers_version='4.4',
pytorch_version='1.6',
py_version='py36',
hyperparameters=hyperparameters
)
SageMaker Metrics¶
SageMaker Metrics can automatically parse the logs for metrics and send those metrics to CloudWatch. If you want SageMaker to parse logs you have to specify the metrics that you want SageMaker to send to CloudWatch when you configure the training job. You specify the name of the metrics that you want to send and the regular expressions that SageMaker uses to parse the logs that your algorithm emits to find those metrics.
# define metrics definitions
metric_definitions = [
{"Name": "train_runtime", "Regex": "train_runtime.*=\D*(.*?)$"},
{"Name": "eval_accuracy", "Regex": "eval_accuracy.*=\D*(.*?)$"},
{"Name": "eval_loss", "Regex": "eval_loss.*=\D*(.*?)$"},
]
# create the Estimator
huggingface_estimator = HuggingFace(
entry_point='train.py',
source_dir='./scripts',
instance_type='ml.p3.2xlarge',
instance_count=1,
role=role,
transformers_version='4.4',
pytorch_version='1.6',
py_version='py36',
metric_definitions=metric_definitions,
hyperparameters = hyperparameters)