nroldanf / transformers-neuron-benchmark

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

pLM on AWS Neuron Devices Benchmark Results

Index πŸ“‹

  1. Introduction πŸ“Œ
  2. Benchmark Setup πŸ› οΈ
  3. Benchmark Tasks πŸ“Š
  4. Benchmark Results πŸ“ˆ
  5. Discussion πŸ’¬
  6. Conclusion πŸŽ‰
  7. Recommendations πŸ“
  8. Acknowledgments πŸ™
  9. References πŸ”

Introduction

This document presents the benchmark results of some of most common Protein Language Models (PLM) on two different devices: GPU and AWS Neuron Devices. The benchmark includes training and inference tasks using Protein Language Models.

The models are:

Model #Params Attention Heads
protBERT 419.933.186 16
prot_t5_xl_uniref50 2.820.144.130 32
esm1b_t33_650M_UR50S 652.359.063 33
esm2_t6_8M_UR50D 7.840.763 6
esm2_t12_35M_UR50D 33.993.843 12
esm2_t30_150M_UR50D 148.796.763 30
esm2_t33_650M_UR50D 652.356.503 33
esm2_t36_3B_UR50D 2,841,632,163 36
esm2_t48_15B_UR50D

Benchmark Setup

  • Start a EC2 instance according to the following table.
Task Device EC2 Instance
Training GPU g4dn.4xlarge
Inference GPU g4dn.4xlarge
Training Neuron trn1.2xlarge
Inference Neuron inf2.8xlarge
  • Run setup
  • Build the docker image
  • Run the image in interactive mode.
  • Run the benchmark scripts.
torchrun --nproc_per_node=2 trainer_api_cli.py facebook/esm2_t6_8M_UR50D --device neuron

If want to skip the compilation before training:

Follow this guide here

neuron_parallel_compile is an utility to extract graphs from trial run of your script, perform parallel compilation of the graphs, and populate the persistent cache with compiled graphs. Your trial run should be limited to about 100 steps, enough for the utility to extract the different graphs needed for full execution. To avoid hang during extraction, please make sure to use xm.save instead of torch.save to save checkpoints. After parallel compile, the actual run of your script will be faster since the compiled graphs are already cached. There may be additional compilations due to unreached execution paths, or changes in parameters such as number of data parallel workers.

neuron_parallel_compile torchrun --nproc_per_node=1 trainer_api.py facebook/esm2_t6_8M_UR50D --device neuron --epochs 0.1 --seed 42 --neuron-cache-url s3://nicolas-loka-bucket/neuron/esm2_t6_8M_UR50D

Follow this guide here

neuronx-cc compile <model-files.hlo.pb> --framework XLA --target trn1 --model-type transformer --auto-cast none --optlevel 2 --output esm.neff --verbose info

Benchmark Tasks

The benchmark comprises the following tasks:

  1. Training using Protein Language Models.
  2. Inference using Protein Language Models.

Benchmark Results

1. Training Results

GPU

  • Training Time: [Insert time taken for training on GPU]
  • Throughput: [Insert throughput achieved during training on GPU]
  • Accuracy: [Insert accuracy achieved during training on GPU]

AWS Neuron Device

  • Training Time: [Insert time taken for training on AWS Neuron Device]
  • Throughput: [Insert throughput achieved during training on AWS Neuron Device]
  • Accuracy: [Insert accuracy achieved during training on AWS Neuron Device]

2. Inference Results

GPU

  • Inference Time: [Insert time taken for inference on GPU]
  • Throughput: [Insert throughput achieved during inference on GPU]

AWS Neuron Device

  • Inference Time: [Insert time taken for inference on AWS Neuron Device]
  • Throughput: [Insert throughput achieved during inference on AWS Neuron Device]

Discussion

[Insert discussion of the benchmark results, including any insights gained from comparing performance on the two devices.]

Conclusion

[Insert concluding remarks summarizing the performance of the deep learning framework on GPU and AWS Neuron Device for training and inference tasks using Protein Language Models.]

Recommendations

[Insert any recommendations for optimizing performance on both devices based on the benchmark results.]

Acknowledgments

[Insert any acknowledgments for contributors, resources, or funding related to the benchmarking process.]

References

[Insert any references to relevant literature, tools, or methodologies used in conducting the benchmark.]

About


Languages

Language:Python 88.1%Language:Makefile 7.7%Language:Shell 4.2%