[Feature Question] Support for simulating multiple concurrent training jobs (Multi-tenancy)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 184
- Avg merge
- 13h 4m
- Merged PRs (30d)
- 1
Description
Hello! I am currently exploring SimAI for research into data center network congestion and topology optimization. I've successfully used SimAI for previous single job research explorations, but I am looking to simulate multi-tenant scenarios similar to those described in the Crux paper (SIGCOMM '24).
Specifically, I want to observe the internode network contention that occurs when two different training jobs (e.g., Job A and Job B) are running simultaneously on the same cluster fabric. Looking at the current documentation and workload format, SimAI appears designed to simulate a single monolithic job at a time, where all ranks belong to one global communicator.
Native Support: Does SimAI currently support defining multiple independent jobs with different start times or independent communicators in a single simulation run?
Manual Workaround: If native scheduling isn't supported, is there a recommended approach to manually "merge" two workloads into a single workload?
Context: My goal is to measure how the placement of independent jobs affects Flow Completion Time and Queue Depth at the ToR/Spine level. I want to verify if SimAI can capture the interference between these independent traffic patterns.
Thank you for your help!
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 by reviewing the current documentation and workload format to determine whether one simulation can represent independent jobs, different start times, and separate communicators. Done means establishing native support or documenting a workable merged-workload approach for measuring contention, Flow Completion Time, and Queue Depth.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100