AstraSimNetwork Initialization nodes_num
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 184
- Avg merge
- 13h 4m
- Merged PRs (30d)
- 1
Description
Hi,
I am wondering whether nodes_num is correct between Line 289 and Line 324 in the simulation setup. This would involve NVSwitches also in the Sys and Workload configurations.
Shouldn't it be gpu_num? Could anyone help me understand this please?
Changing it to gpu_num resolves Issue #44 but it appears that only ncclFlowRingModel is supported at the moment. Any other configuration simply ends the simulation without launching any flows.
Is there any way to run astra-sim native algorithms e.g., double binary tree or direct?
Thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in astra-sim-alibabacloud/astra-sim/network_frontend/ns3/AstraSimNetwork.cc at lines 289-324 and compare how nodes_num and gpu_num are used in the Sys and Workload configurations. Reproduce the Issue #44 behavior with ncclFlowRingModel and another configuration, then determine whether native algorithms such as double binary tree or direct launch flows; done means the node-count behavior and supported configurations are documented or corrected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100