Skip to content
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

Jump to bottom

Proposal to merge "Training Orchestration", "Computation Load Distribution", and "Computation Optimisation" into two separate sections #639

Open
zhimin-z opened this issue Mar 3, 2025 · 0 comments
Open

Proposal to merge "Training Orchestration", "Computation Load Distribution", and "Computation Optimisation" into two separate sections #639

zhimin-z opened this issue Mar 3, 2025 · 0 comments
Assignees
@axsaucedo

Comments

@zhimin-z
Copy link
Collaborator

zhimin-z commented Mar 3, 2025 •
edited
Loading

Currently, there are a great overlapping between these three sections, especially when there are tools, such as DeepSpeed, PaddlePaddle, PyTorch Lightning, awkwardly falling under "Computation Load Distribution".... rather than "Training Orchestration"

Thus, I propose to merge them into two separate sections: 1. Computation Optimisation, 2. Model Training, to make the conceptual boundary clearer.
@zhimin-z zhimin-z changed the title Proposal to merge "Training Orchestration", "Computation Load Distribution", and "Optimized Computation" into two separate sections Proposal to merge "Training Orchestration", "Computation Load Distribution", and "Computation Optimisation" into two separate sections Mar 3, 2025
@zhimin-z zhimin-z pinned this issue Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@axsaucedo axsaucedo

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@axsaucedo @zhimin-z