Skip to content

[Doc] Add Olive link and auto-selection info to optimization note #259

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
yeelam-gordon wants to merge 1 commit into
base: docs
Choose a base branch
from
Open

[Doc] Add Olive link and auto-selection info to optimization note #259

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/new-windows-ml/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ This eliminates the need to:
- Handle execution provider updates manually

> [!NOTE]
> You're still responsible for optimizing your models for different hardware. Windows ML handles execution provider distribution, not model optimization. See [AI Toolkit](https://code.visualstudio.com/docs/intelligentapps/modelconversion) and the [ONNX Runtime Tutorials](https://onnxruntime.ai/docs/tutorials/) for more info on optimization.
> Windows ML automatically selects the best execution provider for your hardware, but you're still responsible for optimizing your models. Combining hardware-aware model optimization with the right execution provider yields the best inference performance. See [AI Toolkit](https://code.visualstudio.com/docs/intelligentapps/modelconversion), [Olive](https://microsoft.github.io/Olive/), and the [ONNX Runtime Tutorials](https://onnxruntime.ai/docs/tutorials/) for more info on model optimization.

## Performance optimization

Expand Down