Accelerated document embeddings with Hugging Face Transformers and AWS Inferentia
notebook: sentence-transformers-huggingface-inferentia
The adoption of BERT and Transformers continues to grow. Transformer-based models are now not only achieving state-of-the-art performance in Natural Language Processing but also for Computer Vision, Speech, Time-Series and especially Semantic Search. 💬 🖼 🎤 ⏳
Semantic search seeks to improve search accuracy by understanding the content of the search query. The idea behind semantic search is to embed all documents into a vector space. At search time, the query is embedded into the same vector space and the closest embeddings are found. Transformers have taken over this domain and are currently achieving state-of-the-art performance but they are often slow and search shouldn’t be slow to feel natural.
AWS's take to solve the performance challenge was to design a custom machine learning chip designed for optimized inference workload called AWS Inferentia. AWS says that AWS Inferentia “delivers up to 80% lower cost per inference and up to 2.3X higher throughput than comparable current generation GPU-based Amazon EC2 instances.”
The real value of AWS Inferentia instances compared to GPU comes through the multiple Neuron Cores available on each device. A Neuron Core is the custom accelerator inside AWS Inferentia. Each Inferentia chip comes with 4x Neuron Cores. This enables you to either load 1 model on each core (for high throughput) or 1 model across all cores (for lower latency).
In this end-to-end tutorial, you will learn how to speed up Sentence-Transformers like SBERT for creating sentence embedding using Hugging Face Transformers, Amazon SageMaker, and AWS Inferentia to achieve sub 5ms latency and up to 1000 requests per second per instance.
You will learn how to:
- 1. Convert your Hugging Face sentence transformers to AWS Neuron (Inferentia)
- 2. Create a custom
inference.py
script forsentence-embeddings
- 3. Create and upload the neuron model and inference script to Amazon S3
- 4. Deploy a Real-time Inference Endpoint on Amazon SageMaker
- 5. Run and evaluate Inference performance of BERT on Inferentia
Let's get started! 🚀
If you are going to use Sagemaker in a local environment (not SageMaker Studio or Notebook Instances). You need access to an IAM Role with the required permissions for Sagemaker. You can find here more about it.
1. Convert your Hugging Face Sentence Transformers to AWS Neuron
We are going to use the AWS Neuron SDK for AWS Inferentia. The Neuron SDK includes a deep learning compiler, runtime, and tools for converting and compiling PyTorch and TensorFlow models to neuron compatible models, which can be run on EC2 Inf1 instances.
As a first step, we need to install the Neuron SDK and the required packages.
Tip: If you are using Amazon SageMaker Notebook Instances or Studio you can go with the conda_python3
conda kernel.
After we have installed the Neuron SDK we can convert load and convert our model. Neuron models are converted using torch_neuron
with its trace
method similar to torchscript
. You can find more information in our documentation.
We are going to use the sentence-transformers/all-MiniLM-L6-v2 model. It maps sentences & paragraphs to a 384 dimensional dense vector space and can be used for tasks like clustering or semantic search.
At the time of writing, the AWS Neuron SDK does not support dynamic shapes, which means that the input size needs to be static for compiling and inference.
In simpler terms, this means when the model is compiled with an input of batch size 1 and sequence length of 16. The model can only run inference on inputs with the same shape.
When using a t2.medium
instance the compiling takes around 2-3 minutes
2. Create a custom inference.py script for sentence-embeddings
The Hugging Face Inference Toolkit supports zero-code deployments on top of the pipeline feature from 🤗 Transformers. This allows users to deploy Hugging Face transformers without an inference script [Example].
Currently is this feature not supported with AWS Inferentia, which means we need to provide an inference.py
for running inference.
If you would be interested in support for zero-code deployments for inferentia let us know on the forum.
To use the inference script, we need to create an inference.py
script. In our example, we are going to overwrite the model_fn
to load our neuron model and the predict_fn
to create a sentence-embeddings pipeline.
If you want to know more about the inference.py
script check out this example. It explains amongst other things what the model_fn
and predict_fn
are.
We are using the NEURON_RT_NUM_CORES=1
to make sure that each HTTP worker uses 1 Neuron core to maximize throughput.
3. Create and upload the neuron model and inference script to Amazon S3
Before we can deploy our neuron model to Amazon SageMaker we need to create a model.tar.gz
archive with all our model artifacts saved into tmp/
, e.g. neuron_model.pt
and upload this to Amazon S3.
To do this we need to set up our permissions.
Next, we create our model.tar.gz
.The inference.py
script will be placed into a code/
folder.
Now we can upload our model.tar.gz
to our session S3 bucket with sagemaker
.
4. Deploy a Real-time Inference Endpoint on Amazon SageMaker
After we have uploaded our model.tar.gz
to Amazon S3 can we create a custom HuggingfaceModel
. This class will be used to create and deploy our real-time inference endpoint on Amazon SageMaker.
5. Run and evaluate Inference performance of BERT on Inferentia
The .deploy()
returns an HuggingFacePredictor
object which can be used to request inference.
We managed to deploy our neuron compiled BERT to AWS Inferentia on Amazon SageMaker. Now, let's test its performance of it. As a dummy load test will we loop and send 10000 synchronous requests to our endpoint.
Let's inspect the performance in cloudwatch.
The average latency for our MiniLM model is 3-4.5ms
for a sequence length of 128.
Delete model and endpoint
To clean up, we can delete the model and endpoint.
Conclusion
We successfully managed to compile a Sentence Transformer to an AWS Inferentia compatible Neuron Model. After that we deployed our Neuron model to Amazon SageMaker using the new Hugging Face Inference DLC. We managed to achieve 3-4.5ms
latency per neuron core, which is faster than CPU in terms of latency, and achieves a higher throughput than GPUs since we ran 4 models in parallel. We can achieve an throughput of up to 1000 documents per second with a 4ms latency on a 128 sequence length per inf1.xlarge
instance, which costs around ~200$ per month.
If you or you company are currently using a Sentence Transformers for semantic search tasks (document-emebddings, sentence-embeddings, ranking), and 3-4.5ms latency meets your requirements you should switch to AWS Inferentia. This will not only save costs, but can also increase efficiency and performance for your models.
We are planning to do a more detailed case study on cost-performance of transformers in the future, so stay tuned!
Also if you want to learn more about accelerating transformers you should also check out Hugging Face optimum.
Thanks for reading! If you have any questions, feel free to contact me, through Github, or on the forum. You can also connect with me on Twitter or LinkedIn.