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.

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

Dangerous advice: it looks that by default the dataset is at /data/milatmp1 #18

Closed
dmitriy-serdyuk opened this issue Mar 24, 2018 · 5 comments
Assignees

Comments

@dmitriy-serdyuk
Copy link
Collaborator

If this is true, Fred is not going to be happy when a lot of people will be hammering NFS.

Given that an experiment is run by a magic script, it is simple to copy data to /Tmp.

@rdevon
Copy link
Owner

rdevon commented Apr 5, 2018

Wait, where is milatmp1 defaulting?

@dmitriy-serdyuk
Copy link
Collaborator Author

In the readme:

torchvision_data_path: /data/milatmp1/hjelmdev/data/

@rdevon
Copy link
Owner

rdevon commented Apr 6, 2018

Ah, right. So one function I need to implement is to designate a local path to which the data is copied before training. Haven't gotten around to it, but I can add it to the todos

@rdevon rdevon closed this as completed Apr 6, 2018
@rdevon rdevon reopened this Apr 6, 2018
@rdevon rdevon self-assigned this Apr 6, 2018
@nouiz
Copy link
Collaborator

nouiz commented Apr 13, 2018

If you have a quick implementation, then good. Otherwise, we are planning to have the local computer cache the networks file system. All new computer we plan to buy will have the hardware for this. Currently, there is a flag to our slurm config to go on computer configured like this.

@rdevon rdevon closed this as completed Jun 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants
@nouiz @rdevon @dmitriy-serdyuk and others