This hands-on walks you through fine-tuning an open source SLM/LLM on Azure and serving the fine-tuned model on Azure. It is intended for Data Scientists and ML engineers who have experience with fine-tuning but are unfamiliar with Azure ML and Mlflow. This hands-on is suitable for the following purposes:
- Half-day workshop or 1-day workshop
- Hackathon starter code
- Reference guide for SLM fine-tuning&serving PoC/Prototype
Before starting, you should meet the following requirements:
-
Azure ML getting started: Connect to [Azure ML] workspace and get your <WORKSPACE_NAME>, <RESOURCE_GROUP> and <SUBSCRIPTION_ID>.
-
Azure AI Studio getting started: Create a project
-
[Compute instance - for code development] A low-end instance without GPU is recommended: **[Standard_E2as_v4] (AMD 2 cores, 16GB RAM, 32GB storage) or [Standard_DS11_v2] (Intel 2 cores, 14GB RAM, 28GB storage, No GPUs)
-
[Compute cluster - for SLM/LLM fine-tuning] A single NVIDIA A100 GPU ([Standard_NC24ads_A100_v4]) is recommended. If you do not have a dedicated quota or are on a tight budget, choose [Low-priority VM].
-
[SLM/LLM deployment] Two NVIDIA V100 GPUs ([Standard_NC6s_v3]) or two NVIDIA A100 GPUs ([Standard_NC24ads_A100_v4]) are recommended.
Note
For managed online endpoints, [Azure ML reserves 20% of the quota for the deployment].1 If you request a given number of instances for those VM SKUs in a deployment, you must have a quota for ceil(1.2 × number of instances requested for deployment) × number of cores for the VM SKU
available to avoid getting an error. For example, if you request 1 instances of a Standard_NC6s_v3
VM (that comes with six cores) in a deployment, you should have a quota for 12 cores (ceil(1.2 × 1 instances) = 2, 2 × 6 cores) available.
- Create your compute instance. For code development, we recommend
Standard_DS11_v2
(2 cores, 14GB RAM, 28GB storage, No GPUs). - Open the terminal of the CI and run:
git clone https://github.com/Azure/slm-innovator-lab.git conda activate azureml_py310_sdkv2 pip install -r requirements.txt
- Choose the model to use for your desired use case.
- Phi-3, Phi-3.5
- [Option 1. MLflow] Run
1_training_mlflow.ipynb
and2_serving.ipynb
, respectively. - [Option 2. Custom] Run
1_training_custom.ipynb
and2_serving.ipynb
, respectively. - (Optional) If you are interested in LLM dataset preprocessing, see the hands-ons in
phi3/dataset-preparation
folder.
- [Option 1. MLflow] Run
- Florence2-VQA
- Run
1_training_mlflow.ipynb
and2_serving.ipynb
, respectively.
- Run
- Don't forget to edit the
config.yml
.
- Phi-3, Phi-3.5
- Finetune Small Language Model (SLM) Phi-3 using Azure ML
- microsoft/Phi-3-mini-4k-instruct: This is Microsoft's official Phi-3-mini-4k-instruct model.
- microsoft/Phi-3-mini-128k-instruct: This is Microsoft's official Phi-3-mini-128k-instruct model.
- microsoft/Phi-3.5-mini-instruct: This is Microsoft's official Phi-3.5-mini-instruct model.
- microsoft/Phi-3.5-MoE-instruct: This is Microsoft's official Phi-3.5-MoE-instruct model.
- Korean language proficiency evaluation for LLM/SLM models using KMMLU, CLIcK, and HAE-RAE dataset
- daekeun-ml/Phi-3-medium-4k-instruct-ko-poc-v0.1
- Fine-tuning Florence-2 for VQA (Visual Question Answering) using the Azure ML Python SDK and MLflow
- Hugging Face Blog - Finetune Florence-2 on DoCVQA
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.
This sample code is provided under the MIT-0 license. See the LICENSE file.
Footnotes
-
This extra quota is reserved for system-initiated operations such as OS upgrades and VM recovery, and it won't incur cost unless such operations run. ↩