Support benchmark using prebuilt artifacts
@huydhn がすでに取り組んでいます。
2025年2月6日 から。
- 主要言語
- Python
- スター
- 5k
- フォーク
- 1.2k
- 平均マージ
- 2日 10時間
- マージ済み PR(30日)
- 581
説明
🚀 The feature, motivation and pitch
Enable this for on-demand workflow only, to offer developers additional flexibility and efficiency.
Scenarios where benchmarking w/ prebuilt artifacts are needed:
- Sometimes the pte model may come from outside, for example the model may come from external partners. Or the model is downloaded from the executorch community from Hugging Face, https://huggingface.co/executorch-community/DeepSeek-R1-Distill-Llama-8B/tree/main.
- Developers who work on the runtime may not necessarily to re-export the same model all the time.
- Developers who work on exporting may not need to build the banchmark app all the time
UX:
- via GitHub UI
- via script
Source of the artifacts to be used in the benchmark workflow:
- pte models from Hugging Face, e.g. https://huggingface.co/executorch-community/Llama-3.2-1B-Instruct-ET/tree/main
- From S3 (uploaded by developers/users)
We will need to define the UX to support this feature. For example, allow users to upload prebuilt artifacts via script. The script will return with links to the artifacts. Then users can schedule an on-demand workflow via UI, or users can do everything via the script.
Policy and TTL to keep the uploaded artifacts.
CC: @digantdesai @kimishpatel @cccclai
Alternatives
No response
Additional context
No response
RFC (Optional)
No response
cc @huydhn @kirklandsign @shoumikhin @mergennachin @byjlw
コントリビューションガイド
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
評価
この issue はまだ評価されていません。