[BACKEND-1] No backend-selection rubric; auto-selection behavior is opaque
Open
Documentation
- Dominant language
- Python
- Stars
- 2k
- Forks
- 561
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 145
Description
## Problem
The documentation explains that auto-selection between the DTensor and Megatron backends exists but does not provide a general rubric for when each will be chosen. Users have no intuition for which backend will run for their workload and cannot make informed decisions about overriding the default.
## Suggested fix
Add a backend-selection rubric to the training backend documentation. Include guidance such as model size thresholds, tensor parallelism requirements, and use cases where each backend is preferred.
Contributor guide
Assessment
This issue has not been assessed yet.