Separate working directory from job command

stanford-futuredata / gavel

Code for "Heterogenity-Aware Cluster Scheduling Policies for Deep Learning Workloads", which appeared at OSDI 2020

MIT License

125 stars 31 forks source link

Separate working directory from job command #200

Closed santhnm2 closed 4 years ago

santhnm2 commented 4 years ago

Not a huge fan of having gpusched in the directory names -- for example, this repository is now called gavel? Can we use relative paths instead?

Yea so I am using relative paths in job_table.py, but the pre-generated traces do have gpusched hardcoded. I can try to fix that but can I do it in a separate PR? This one is starting to get messy